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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzY0IiwiaGFzaCI6IjEwMDMzNTNjLWNmZjQtNGRkNS05ZWNlLWNjYTZmYWUzZGJhOSJ9
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.
Another note to be considered is VMware is also unable to snapshot PRDM’s.
More information
Here is a KB on understanding how VMWare snapshots work: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180
KB ID:
1764
Product:
Veeam Backup & Replication
Version:
5.x, 6.x, 7.x
Published:
2013-05-30
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
