{"id":9655,"date":"2020-08-11T19:09:23","date_gmt":"2020-08-11T09:09:23","guid":{"rendered":"https:\/\/nsrd.info\/blog\/?p=9655"},"modified":"2020-08-11T19:09:26","modified_gmt":"2020-08-11T09:09:26","slug":"avamar-basics-vmware-changed-block-tracking-recoveries","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2020\/08\/11\/avamar-basics-vmware-changed-block-tracking-recoveries\/","title":{"rendered":"Avamar Basics \u2013\u00a0VMware Changed Block Tracking Recoveries"},"content":{"rendered":"\n

One of the most useful recoveries you can do in Avamar, NetWorker or PowerProtect Data Manager is the changed block tracking<\/em> recovery.<\/p>\n\n\n\n

Within VMware, a changed block tracking (CBT) recovery is what you do when a virtual machine has been damaged or corrupted. Either there’s no option to fix it, or the time it would take to somehow dive into the operating system and repair the damage is too much. You.Just.Need.It.Back.<\/em><\/p>\n\n\n\n

If you’re recovering a virtual machine to an entirely new VM, you’re going to have to read the entire VM from storage. So a 1TB virtual machine requires 1TB of data being read from your protection storage.<\/p>\n\n\n\n

On the other hand, a CBT recovery compares the differences between the VM’s blocks on disk now, and what’s stored in the backup you’ve selected. The blocks that are the same between the copy on disk and the protection storage copy aren’t recovered. Why waste time? Instead, we only need to recover data for blocks that have changed since the backup.<\/p>\n\n\n\n

So if you’ve got a 1TB virtual machine that had some patching done on it and it now won’t boot, or someone has done a ahem<\/em> boo-boo within the VM, it could be that there’s only hundreds of megabytes<\/em> that have changed since the backup. That can be a huge difference in the time it takes to complete.<\/p>\n\n\n\n

In the video below, I’ll take you through the CBT recovery process.<\/p>\n\n\n\n

\n