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

Veeam disk exclusions and how they work with VMware snapshots

Challenge

A VMware snapshot is snapping an entire VM even though we have excluded some of the VMDKs in Veeam’s job properties.

Cause

When Veeam issues the Snapshot API call, we will still snapshot the entire VM. This is done through VMware. We will still only backup the selected VMDK’s however.

Solution

To solve, you can set the excluded VMDK’s in VMware for the selected VM as independent. Independent disks are unable to have snapshots taken of them.

Another note to be considered is VMware is also unable to snapshot PRDM’s.

More information

KB ID:
1764
Product:
Veeam Backup & Replication
Version:
5.x, 6.x, 7.x
Published:
2013-05-30
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