VMware quietly posted this KB article (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2090639). Essentially if your VMs disk was smaller than 128gig and was expanded past 128gig the VMs backups may be at risk.
We use Veeam and CBT heavily in my environment and this is a bit of a PITA for us as many of my VMs have scaled up from a much smaller size. In order to help fix the problem I am using the below script. This sets the CBT value to $false, takes a snapshot, and then removes the snapshot to “stun” the VM.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
$choice = Read-Host 'Press 1 to select a VM, Press 2 to select a Cluster, press 3 to choose a Folder' switch ($choice) { 1 { $vmName = Read-Host 'Please type in a VM name to reset CBT on.' $vmInfo = Get-vm $vmName $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $spec.ChangeTrackingEnabled = $false $vmInfo.ExtensionData.ReconfigVM($spec) $snap=$vmInfo | New-Snapshot -Name 'Disable CBT' $snap | Remove-Snapshot -confirm:$false } 2 { $vmName = Read-Host 'Please type in a Cluster name to reset CBT on.' $vmInfo = Get-Cluster $vmName | Get-VM $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $spec.ChangeTrackingEnabled = $false $vmInfo.ExtensionData.ReconfigVM($spec) $snap=$vmInfo | New-Snapshot -Name 'Disable CBT' $snap | Remove-Snapshot -confirm:$false } 3 { $vmName = Read-Host 'Please type in a Folder name to reset CBT on.' $vmInfo = Get-Folder $vmName | Get-VM $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $spec.ChangeTrackingEnabled = $false $vmInfo.ExtensionData.ReconfigVM($spec) $snap=$vmInfo | New-Snapshot -Name 'Disable CBT' $snap | Remove-Snapshot -confirm:$false } default {Write-host 'Invaild Input, exiting...'} } |