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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODQ0IiwiaGFzaCI6IjFmYjM5NWQ2LWE2OGYtNGM3YS1iODBjLTJjY2M0ZWIzOWU2MyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Hyper-V VSS snapshot import delay

Challenge

If you backup your VMs using Dell Equallogic hardware VSS provider in some cases data(vhd/vhdx) that we read from VSS snapshot could be inconsistent

Cause

During Hyper-V backup, we execute VSS API call DoSnapshotSet, as soon as it completes, we execute ImportSnapshot VSS API call, without any delay between two API calls.
Apparently Dell VSS hardware provider continues to write some data to VSS snapshot after execution of DoSnapshotSet method(after returning S_OK code), and if we try to immediately import VSS snapshot, we could backup inconsistent data from that VSS snapshot.

Solution

In order to workaround this problem we introduce a timeout/delay between execution of ImportSnapshot VSS API call
Open registry editor on Veeam Backup console
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Create DWORD parameter:
HvDelayBeforeSnapshotImportCompleteSec
Set it to 90 seconds(or more if your hardware VSS provider requires more time).

KB ID:
1844
Product:
Veeam Backup & Replication
Version:
7.x
Published:
2013-12-18
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later