1-800-691-1991 | 9am - 8pm ET
EN

VMs stored on vVols may experience a significant stun during the snapshot removal process after the backup session.

KB ID: 3055
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2019-11-22
Last Modified: 2021-06-03

Challenge

During the snapshot removal operation that occurs at the end of a backup/replication job for a VM stored on a vVol Datastore, the following is observed:

  • The Guest OS of the VM being processed is stunned or frozen.
  • Monitoring software may report that the Guest OS is inaccessible due to a lack of ping response.

Cause

The snapshot removal process hangs as it waits for the volume unbind on the ESXi host. This issue can occur with any ESXi configuration using vVols on vCenter 6.0 and later versions.

This occurs when the following factors are combined:

Solution

Starting with Veeam Backup & Replication v9.5 U3 (9.5.0.1536), a setting was added to allow for the configuration of a delay between the detachment of hotadded disks and the request for snapshot removal. This delay can be configured using the following registry value:

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: HotaddTimeoutAfterDetachSec 
Value Type: DWORD (32-bit) Value 
Value Data: 60

The delay is measured in seconds and may need additional adjustment based on the environment. In most cases, 60 seconds has been plenty of time for disks to detach from the proxy before the snapshot removal request was issued. A smaller delay may also work. However, it is possible that in some environments, a larger delay may be required.

KB ID: 3055
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5
Published: 2019-11-22
Last Modified: 2021-06-03

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.