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

Veeam Backup Temporary Snapshot

Challenge

One or more snapshots are present on a VM, impacting performance.

Cause

When Veeam Backup & Replication begins a backup or replication job, it sends a VIM API command to the vCenter (or standalone host) to create a snapshot with the name "VEEAM BACKUP TEMPORARY SNAPSHOT ". At the end of the backup or replication job, Veeam Backup & Replication sends another API command to remove that snapshot. In some cases, this command will not be received, or in rarer cases it will not be executed.
 
This can be due to network connectivity issues between the Veeam Backup & Replication server and the vCenter, connectivity issues between the vCenter and the ESXi host, or more rarely due to a malfunction on the vCenter or host.
 
If the backup job did not complete due to power loss or failure of the Veeam Backup Service, the snapshot removal command will not be sent.

Solution

If these snapshots are present when the backup or replication job is not running, they can be safely removed using the Delete or Delete All buttons in the Snapshot Manager.

User-added image

In some cases, the snapshot removal will produce an error in vSphere. When that happens you should perform troubleshooting based on the error message, or contact VMware support. If the failure to remove the snapshot involves a file lock and you are using the Virtual Appliance transport mode, make sure that the VM disks were removed from the proxy (KB1775).
 
If there are no error messages, this may be an infrastructure issue. Perform the following steps to identify the source of the issue:
  • During the backup job run continuous pings between the Veeam B&R server and the vCenter, or between the Veeam B&R server and the affected host, to determine if packet loss is indicated.
  • Observe resource usage on the Veeam B&R server and on the vCenter server to see if, for example, memory usage is very high.
  • Check event logs on the Veeam server and vCenter server.

More information

  • Do not delete this snapshot until the job is completed.
  • In version 6.5.0.128 and later, Veeam Backup & Replication tracks all snapshots it creates and tries to remove those snapshots on later job runs. Prior to 6.5.0.144, this feature could result in vCenter connection duplication if the temporary snapshot was deleted manually.
  • If the snapshot is named anything other than "VEEAM BACKUP TEMPORARY SNAPSHOT" then this KB is not applicable.
  • Commands to monitor snapshot deletion in ESX 2.5/3.x/4.x and ESXi 3.x/4.x/5.x
KB ID:
1790
Product:
Veeam Backup & Replication
Version:
5.x, 6.x, 7.x, 8.x
Published:
2013-07-09
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