https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyODkwIiwiaGFzaCI6ImJlZmRhYjYwLTUzZWUtNGUwNC1hOGQ1LWJjNTViMjdiNWFjMyJ9
Hyper-V Backup jobs failing with an error "The system cannot find the file specified" after upgrade to Veeam B&R 9.5 Update 4
| KB ID: | 2890 |
| Product: | Veeam Backup & Replication |
| Version: | 9.5.4.2615 |
| Published: | 2019-02-07 |
| Last Modified: | 2021-03-22 |
Challenge
After installing Veeam Backup & Replication 9.5 Update 4, Hyper-V backup without application-aware processing may fail with the error "The system cannot find the file specified".
Version Specific Article
This article is relevant only to Veeam Backup & Replication 9.5.4.2615.
Cause
This issue is caused by the snapshot path in the VM 's configuration being different from the actual path on a file system in terms of symbols capitalization. You can confirm this by comparing paths in bold in the Task.<VM NAME>.<VM UUID>.log file:
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <snapshots>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <data_root type="string">C:\Temp\<VM name></data_root>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <size type="integer">0</size>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </snapshots>
[22.01.2019 19:39:09] <11> Info [AP] (65e8) command: 'file2text\n\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml\n2097152\n'
[22.01.2019 19:39:10] <10> Info [ReconnectableSocket] Stop confirmation was sent on [c1d84e94-b09b-4039-a8dc-4973e12934fc].
[22.01.2019 19:39:10] <23> Error [AP] (65e8) error: The system cannot find the file specified.
[22.01.2019 19:39:10] <23> Error Failed to open file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml] in readonly mode.
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <snapshots>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <data_root type="string">C:\Temp\<VM name></data_root>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <size type="integer">0</size>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </snapshots>
[22.01.2019 19:39:09] <11> Info [AP] (65e8) command: 'file2text\n\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml\n2097152\n'
[22.01.2019 19:39:10] <10> Info [ReconnectableSocket] Stop confirmation was sent on [c1d84e94-b09b-4039-a8dc-4973e12934fc].
[22.01.2019 19:39:10] <23> Error [AP] (65e8) error: The system cannot find the file specified.
[22.01.2019 19:39:10] <23> Error Failed to open file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml] in readonly mode.
Solution
There are two methods for correcting this issue depending on your preference:
1. Install an updated version of Veeam Backup & Replication 9.5 U4b:
- This issue is resolved in Veeam Backup & Replication 9.5.4.2866
- Please download and install the update from https://www.veeam.com/kb2970
2. Change snapshot path in VM configuration manually:
- Connect to the Hyper-V host and go to VM Configuration of VM in question;
- Go to Checkpoints tab and choose ‘Browse…’ underneath the snapshot path;
- Update the path.
| KB ID: | 2890 |
| Product: | Veeam Backup & Replication |
| Version: | 9.5.4.2615 |
| Published: | 2019-02-07 |
| Last Modified: | 2021-03-22 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
