How To Disable - Enab
How To Disable - Enab
When I created a case with EMC Support, they dug into the logs and then pointed to
best practices that recommend disabling CBT when more than 10,000 blocks
regularly change between backups. The problem I hit next was that the top result and
KB for enabling/disabling CBT was a VMware post stating that step 1 was to power
off the VM. Backups are running long and the next maintenance window isn’t for two
weeks. Hmm…
1. Avamar method
2. PowerCLI method
1. Avamar. Then I recalled that Avamar seems to have no issue turning on CBT hot
when adding VMs to its inventory. If it can turn it on, how about turning it off? From
the GUI, the only time it exposes that option is adding a “New Client” in the
Administration panel. To be new, it can’t exist, which either means retiring the active
client or deleting it. Deleting it worked smoothly, but also wiped out all backups (not a
good idea); retiring seemed to hang when adding it back, but sometimes worked.
Getting closer…
Width: 1920
EMC suggested trying the proxycp.jar utility on the utility node. This tool does a lot of
fun stuff with VM clients and their related backup proxies. To download the latest
version (important), use FTP and the link below:
ftp://avamar_ftp:[email protected]/software/scripts/proxycp.jar
Then, upload it via SFTP/SCP to your Avamar utility node and ‘sudo cp’ it to
/usr/local/avamar/bin. After that, SSH to the utility node and run the following
commands to disable CBT and then verify that it worked (or run first to check status):
Width: 1920
2. PowerCLI. “Benj” posted a quick script on this back in 2012 with the full post
available here:
http://www.itwalkthru.com/2012/03/disabling-or-enabling-vmware-
change.html
Others have since pointed to Veeam KB1940 for validation of this method, and
curiously, the exact same script is given. Either both pulled from the same source
(albeit Veeam was two years later), or Veeam pulled from Benj, too. Regardless, here’s
the gem:
Apply the specification to each VM, then create and remove a snapshot:
foreach($vm in $vms){
$vm.ExtensionData.ReconfigVM($spec)
$snap=$vm | New-Snapshot -Name 'Disable CBT'
$snap | Remove-Snapshot -confirm:$false}
If others in the community have any warnings concerning these hot-mods, feel free to
comment. Hopefully this can help those who have otherwise been limited to
downtime changes.
Share this:
Next Post
What’s Involved In Upgrading XtremIO to 3.0?
Chris
TECHNOLOGY VIRTUALIZATION
2 Comments
Chris said:
→
Sam, yes it will create a complete/full snapshot and backup, but your
concern is valid. A new full backup may incur significant
consolidation time, depending on your backup software/target.
The context of this article was Avamar, which wasn’t always quick
about taking full backups. In 2015, I replaced Avamar with Rubrik
Width: 1920
(www.rubrik.com; for whom I now work), which addresses this pain
point of customers (consolidation challenges), among other benefits.
Leave a Reply
Enter your comment here...
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Search... Go
TAGS
3PAR Avamar AWS backup blogging Cisco cloud community compression deduplication Dell
disaster recovery EFI EMC ESXi HP Hyper-V IETF IPv6 load balancing love Microsoft
Width: 1920
Rubrik SSH syslog vCenter VDI Veeam VMFS vMotion VMQ VMUG VMware
The Gurleyman
"It takes a manly man to be a Gurleyman." ~Sommer