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

[TheKaiser]

We have an issue with backup after Update 4 for B&R 9.5

Of the 57 VMs always the same 10 VMs fail

Environment: Windows Server 2016 with Veeam Backup & Replication 9.5.4.2615
Windows Server 2012 R2 Hyper-V Host

Code: Select all

The backup fails with: Failed to open file 
[\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy: 

Code: Select all 30/1/2019 3:33:42 PM :: Processing DEV04 Error: The system cannot find the path specified. 
Failed to open file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12\Virtual Machines\Snapshots\6C8E1C7E-D871-4C02-AF36-143CA3F5C6E7.xml] in readonly mode. 
Failed to open file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12\Virtual Machines\Snapshots\6C8E1C7E-D871-4C02-AF36-143CA3F5C6E7.xml] for reading. 

what we have done so far:

-Create new job with affected VM
-Restart the VMs
-Restart the Hyper-V 2012 Host
-Migrated the affected VM to another host

-Check the with vssadmin list shadows |more

Code: Select all

PS C:\Windows\system32> vssadmin list shadows |more
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

No items found that satisfy the query.

Veeam Support - Case # 03388708 - Error: The system cannot find the file specified

Thanks

[Dima P.]

Hello and welcome Achim!

I've merged your post to the existing discussion. This problem is likely caused by issues with VSS components, so, kindly, keep working with our support team in order to find the root cause. Cheers!

[nikods]

I have the same problem after update to 9.5 update 4. I have three servers in windows server 2012 r2 failover cluster, all of the servers backup jobs are failing, the same day I have updated to update 4 one time all of the jobs have completed and tomorrow they started to fail with error:
Processing SERVERNAME Error: The system cannot find the file specified.
Failed to open file [\\?\GLOBALROOT\Device\CSV.....xml] in readonly mode.
Failed to open file [\\?\GLOBALROOT\Device\CSV.....xml] in for reading.
I try to put VM on same host that holds CSV but same error. I can rescan hosts and check backup files but cant do backup jobs. I try to make new job, same error. I have restarted, reconnected iscsi to csv storage and no change.
Please help

[TheKaiser]

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

[Mike Resseler]

Hi TheKaiser,

Thanks for letting us know. Did you change that path manually or was it this by default?

[nikods]

The manual setting of the paths for Snapshots has resolved the problem form me also!

Thank you All!

Niko

[JSi]

Hi to all,

we have exactly the same problem (Win2012R2 Hyper-V cluster) after updating to U4, unfortunately our support contract expired.
Change of checkpoint path in Failover Cluster Manager unfortunately doesn`t help. Is there any other required condition (backup server reboot, hyper-v node reboot,...)?

Jan

[JSi]

Probably it takes some time. It looks ok now.

[Mike Resseler]

Hi Jan,

Just to be clear: You did the change of the checkpoint path and it didn't work to start with? But now it works? I do believe you need to restart the VM to make the new checkpoint settings applicable. (But not so sure anymore)

[JSi]

Hi Mike,

many of impacted VMs were in offline state. It doesn`t help at first retry, but without any other change, next retry was ok. Thank you for reply.

Anyway Veeam thanx for your work on new update and your general attitude.

J.

[ejenner]

I've got a couple of Hyper-V VMs which won't backup.

Code: Select all

The following error: 04/02/2019 04:05:40 :: Processing SERVERNAME Error: The system cannot find the file specified.
Failed to open file [\\?\Volume{4561c16c-2825-11e9-80c5-2c768a5d7fc0}\SERVERNAME\Snapshots\424D66E2-309E-4ECC-8589-1C691E1E6B5C.xml] in readonly mode.
Failed to open file [\\?\Volume{4561c16c-2825-11e9-80c5-2c768a5d7fc0}\SERVERNAME\Snapshots\424D66E2-309E-4ECC-8589-1C691E1E6B5C.xml] for reading.

The thing both these servers have in common is that they're DMZ servers. The VMs are running from a HP 3PAR and I have Direct SAN backup configured.

I'm guessing this is a blocked ports issue due to the DMZ configuration but just putting it out there for comments / suggestions. Just in case someone has seen it before.

[PTide]

EJ,

Although your config might be a little different (no CSV apparently), this thread seems to be approppriate for your post. Kindly open your own support case and let us know case ID.

Thanks!

[ejenner]

yes, I did see this. Going to have to think about this for a while as although the error message is the same... the symptoms are different.

[Mike Resseler]

Hey EJ,

Most likely it isn't this problem, but I heard yesterday from a friend that his checkpoints got into read-only mode after an AV signature update. Are those checkpoint locations excluded?

[roger_ramjet]

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.

I cannot believe this worked for me!! Mine was slightly different where there was no "Snapshots" folder in the save location. My issue was there were no capital letters where there should have been. Looks like you have to be very specific in regards to capital letters in the whole file name location with Veeam.

EDIT: Also if you're using Hyper-V with Failover Clustering, you have to open "Settings" from the VM in Failover Cluster Manager to change the snapshot path.