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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMjc1IiwiaGFzaCI6ImJkZGNkNTM1LTBhMzYtNDU4OS05MTA5LTAxZDc4MzIxZDVjYSJ9
Cannot find shadow copy of volume
Challenge
Backup job fails with the following error:
Error Cannot find shadow copy of volume VM (X:) (System.Exception)
Cause
The disk ID in Windows has changed since the last backup run and does not match the ID stored in Veeam database. This can happen if the EFI system partition drive has been backed up in the volume mode.
Solution
Reset the database information so that it recognizes the new disk ID from Windows.
To do so without clearing up the database, set the backup job to run a file level backup, adding files that are on an active volume. Run the backup job immediately afterwards. If the job runs successfully, this should mean that the disk ID information has been re-added to the database. It should be safe to change the backup configuration to a volume level backup.
To do so without clearing up the database, set the backup job to run a file level backup, adding files that are on an active volume. Run the backup job immediately afterwards. If the job runs successfully, this should mean that the disk ID information has been re-added to the database. It should be safe to change the backup configuration to a volume level backup.
More information
Another option would be to recreate the local database. For more information on how this can be done, please see the following KB (steps 1 - 4)
KB ID:
2275
Product:
Veeam Agent for Microsoft Windows
Version:
1.x, 2.x
Published:
2017-04-10
Last Modified:
2020-08-13
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
