Host-based backup of VMware vSphere VMs.
Post Reply
Robert G.
Novice
Posts: 7
Liked: 3 times
Joined: Jun 20, 2019 5:59 pm
Location: Germany
Contact:

Behavior of VMware CBT when creating and deleting files immediately

Post by Robert G. »

Will VMware CBT mark blocks as changed if you create a large file (with random data) and delete it immediately afterwards?

Scenario:
1. Veeam full backup
2. Application backup to vmdisk
3. Copy the app backup to a share
4. Removal of the app backup
5. Veeam incremental backup
6. Profit
ronnmartin61
Veeam Software
Posts: 441
Liked: 131 times
Joined: Mar 07, 2016 3:55 pm
Full Name: Ronn Martin
Contact:

Re: Behavior of VMware CBT when creating and deleting files immediately

Post by ronnmartin61 » 2 people like this post

It depends. In a nutshell if the disk block consists entirely of deleted file data and "Exclude deleted file blocks" is enabled in the advanced job settings then the block is not processed. For a full description with affiliated caveats see - https://helpcenter.veeam.com/docs/backu ... ck&ver=120
Robert G.
Novice
Posts: 7
Liked: 3 times
Joined: Jun 20, 2019 5:59 pm
Location: Germany
Contact:

Re: Behavior of VMware CBT when creating and deleting files immediately

Post by Robert G. »

Thank you for your quick reply.
What is the situation with Linux systems?
ronnmartin61
Veeam Software
Posts: 441
Liked: 131 times
Joined: Mar 07, 2016 3:55 pm
Full Name: Ronn Martin
Contact:

Re: Behavior of VMware CBT when creating and deleting files immediately

Post by ronnmartin61 »

I think the "Limitations" section of the helpcenter document is pretty clear that this applies only to Windows VM's + NTFS filesystems. BitLooker for Linux, other Windows filesystem types, etc. is not supported
Robert G.
Novice
Posts: 7
Liked: 3 times
Joined: Jun 20, 2019 5:59 pm
Location: Germany
Contact:

Re: Behavior of VMware CBT when creating and deleting files immediately

Post by Robert G. »

Of course is BiLocker just an Windows topic. I tested the scenario with a Linux VM.
VMware CBT will just mark every block as changed if something happend with it and Veeam will backup these blocks, so even (large) short-term temporary files.
I was hoping that Veeam would check if an operating system marked these blocks as "free" in its (free-space) block bitmap. So that these blocks can then be skipped (even if the block content has changed).

Image

1. inc backup
2. head -c 30G < /dev/urandom > testfile
3. rm testfile
4. wait some minutes
5. inc backup -> 30gb change
Andreas Neufert
VP, Product Management
Posts: 6749
Liked: 1408 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Behavior of VMware CBT when creating and deleting files immediately

Post by Andreas Neufert »

Yes, this is expected. With Windows we compare the file system table and the blocks and remove them.
For most of the files, the files would have existed in the previous backup and when you remove them before the next backup, then based on CBT we would read them again, but our inline deduplication would remove these blocks likely (as they are the same) before they go to the repository. So only for those files that are created and removed between backup sessions we would back them up based on VMware CBT.
Post Reply

Who is online

Users browsing this forum: No registered users and 48 guests