I'm curious if you have tried running sdelete prior to your first svmotion?So turns out I haven't been able to get my empty disk space back by simply svmotioning the thin provisioned disc to another datastore.
Vitaliy S. wrote:If virtual disk size (max capacity) doesn't change, then you will only have large incremental file size on the job run. Zeroing out blocks makes sense when you do full job pass, see this topic for further reading > Unusually large VBK size
Zew wrote:But what about bitlooker?
Zew wrote:My question now is can I easily see this change in vSphere under used space?
Zew wrote:While having bit looker enabled will help shrink backups from veeam perspective, it doesn't on vmwares persecptive.
Zew wrote:So question now is, does bitlooker auto defrag to ensure best results from sdelete (or whatever veeam is using.. if its using vmware tools I wonder if it even indeed works at all) and the only reason I wonder that was cause I did intially try to shrink my disk using vmware tools shrink cmdlet vs sysinternals sdelete.
Zew wrote: After this, would I be forced to do an active full, or will CBT and bitlooker properly pick up on these changes?
Zew wrote:Even on just a defrag part... if you defrag a VM... would the VIB on the next run just be massive as CBT sees all the blocks being moved as changed data to copy??!
Zew wrote:1) Converted my disc to thin via svmotion. No size change seem to be shown.
2) Defrag (currently in progress, reported around 39% fragmented)
3) sdelete -c and then -z
4) shut vm down, run vmkfstools -K location of VMDK (if on localstorage or iSCSI) else svmotion from Datastore (1MB block size) to new datastore (8MB block size)
5) gonna check reported size on vsphere, at this point I'm hoping to see used space equal to that of the quest OS.
Users browsing this forum: No registered users and 1 guest