Clean up CBT after Avamar proxy failure

Posted Jul 6, 2015 Updated Apr 2, 2025

By J Bilinski

1 min read

Using brute-force methods to clean up Avamar VMWare proxy change block tracking and vmdk disconnect failures.

#requires -Version 4 -Modules VMware.VimAutomation.Core #remove shared drives mounted on avamar proxy (ASSUMES SYSTEM DISKS ARE DEFAULT STORED WITH PROXY) Get-VM ava-proxy* | Get-HardDisk | Where-Object -FilterScript {$_.filename -notlike "*$($_.parent)/$($_.parent)*"} | Remove-HardDisk -confirm

#requires -Version 4 -Modules VMware.VimAutomation.Core #Consolidate needed drives (Get-VM | Where-Object -FilterScript {$_.Extensiondata.Runtime.ConsolidationNeeded}).foreach({$_.ExtensionData.ConsolidateVMDisks()})

#requires -Version 4 -Modules VMware.VimAutomation.Core #consolidate ALL snapshots (Get-VM | Where-Object -FilterScript {($_.extensiondata.snapshot.count -ne '0') -and $_.powerstate -eq 'poweredOn'}).foreach({$_.ExtensionData.ConsolidateVMDisks()})

powershell, script, interactive, reference

This post is licensed under CC BY 4.0 by the author.

Trending Tags