* There is a known issue in the default configuration of the VMware Image Dataset for Avamar 5.0.0-407, 5.0.0-409 and 5.0.0-410 that prevents Avamar from using VMware Change Block Tracking to perform incremental backups of VMware virtual disks
* The utilize_change_block_list option is not set by default in this dataset, forcing full backups each time
There are two settings that affect the use of change block tracking. Please follow the instructions below to verify change block tracking is correctly enabled for each client (Item 1 below) and for the VMware Image Backup Dataset (Item 2).
Verify that the "Enable change block tracking" is set in the policy settings for each affected client:
In the Avamar Administrator GUI, open the Policy panel
Select the "Clients" tab above the tree on the left
Select an affected client in the right-hand pane, then click the Edit button
Select the "VMware" tab
If "Enable change block tracking" is not checked, check it
Click "OK" to save the settings
Repeat steps 3 through 6 for any other affected clients
Adjust the settings of the default VMware Image Dataset to utilize the changed block list:
In the Avamar Administrator GUI, select Tools => Manage Datasets... from the menu bar
Select the VMware Image Dataset in the tree on the left
Click "Edit" to edit the dataset
Select the "Options" tab
In the "Select Plug-In Type" dropdown menu, select "Windows VMware Image"
Verify that "Use change block tracking to increase performance" is checked
Click "OK" to save the settings
Two "utilize_changed_block_list=true" entries should appear in the Options section of the dataset editor - one for the Linux plugin and one for the Windows plugin
Click "OK" to save your changes
This issue was corrected in Avamar Server version 5.0.1-32.
Please Note: After enabling change block tracking, one additional full backup will be run to generate a change block list. Subsequent backups should run as incremental backups.
Thanks Rudy, I had checked that previously, but I found out that it is an issue of having VM snapshots older than when CBT was enabled in VMware. Avamar ignores the CBT if it detects that previous snapshots are available. We resolved it by deleting all snapshots in vmware that were previous to CBT being enabled. Thanks everyone for the help. There is more information available here: http://vmguy.com/wordpress/index.php/archives/1538
Hormigo
2 Intern
•
131 Posts
0
November 17th, 2010 06:00
Hi,
What is CBT?
Did you mean VCB?
Regards,
Hormifo
rob_steele
1 Rookie
•
120 Posts
0
November 17th, 2010 07:00
Hormigo,
CBT is change block tracking which is a feature of VMware. Avamar uses CBT for image level backups. I hope that answers your question.
5uR68oOE7d12317
48 Posts
0
November 17th, 2010 07:00
Rob,
* There is a known issue in the default configuration of the VMware Image Dataset for Avamar 5.0.0-407, 5.0.0-409 and 5.0.0-410 that prevents Avamar from using VMware Change Block Tracking to perform incremental backups of VMware virtual disks
* The utilize_change_block_list option is not set by default in this dataset, forcing full backups each time
There are two settings that affect the use of change block tracking. Please follow the instructions below to verify change block tracking is correctly enabled for each client (Item 1 below) and for the VMware Image Backup Dataset (Item 2).
This issue was corrected in Avamar Server version 5.0.1-32.
Please Note: After enabling change block tracking, one additional full backup will be run to generate a change block list. Subsequent backups should run as incremental backups.
Thanks
rob_steele
1 Rookie
•
120 Posts
0
November 17th, 2010 07:00
Thanks Rudy, I had checked that previously, but I found out that it is an issue of having VM snapshots older than when CBT was enabled in VMware. Avamar ignores the CBT if it detects that previous snapshots are available. We resolved it by deleting all snapshots in vmware that were previous to CBT being enabled. Thanks everyone for the help. There is more information available here: http://vmguy.com/wordpress/index.php/archives/1538