Browse Community
Help
Log In
Responses(1)
Solutions(1)
ble1
4 Operator
•
14.4K Posts
0
October 23rd, 2014 17:00
cbt first needs to be enabled on VMware side (be aware of VMware KB: Enabling Change Block Tracking in vSphere 5.5 fails). Unlike Veeam, NW won't enable CBT on hypervisor as that is something ESX admin should do and there might be reasons why they even do not wish to use it. So, to my knowledge, you need to enable it yourself. I would suggest to read http://www.virtualizationsoftware.com/using-vsphere-changed-block-tracking-emc-networker-backup/ too.
Dell Support Resources
View All
Top
ble1
4 Operator
•
14.4K Posts
0
October 23rd, 2014 17:00
cbt first needs to be enabled on VMware side (be aware of VMware KB: Enabling Change Block Tracking in vSphere 5.5 fails). Unlike Veeam, NW won't enable CBT on hypervisor as that is something ESX admin should do and there might be reasons why they even do not wish to use it. So, to my knowledge, you need to enable it yourself. I would suggest to read http://www.virtualizationsoftware.com/using-vsphere-changed-block-tracking-emc-networker-backup/ too.