CBT Reset KB1113 : Changed procedure

[Alan_ORiordan]

Hi

We have suffered two power cuts this week and may have to run the CBT reset procedure if this cannot be reset automatically. The article has been updated in May and the procedure has changed to require one less power down.

Previously these were the steps:

The following steps will reset CBT on the guest VM:

1. Power off the VM
2. Right click the VM, click "Edit settings", find the "Options" tab and click "Configuration Parameters"
3. Set the "ctkEnabled" value to false
4. Set the "scsi0:x.ctkEnabled" value to false for each disk of the VM in question
5. Open the source folder and remove any -CTK.VMDK files
6. Power on the VM and power it off again
7. Set the "scsi0:x.ctkEnabled" value back to true for each disk of the VM in question
8. Power the VM on
9. Rerun Backup or Replication job to re-enable CBT

Note steps 6 and 7

Now the procedure is:

1. Power off the VM.
2. Right-click the VM, click [Edit settings], click the Options tab, select the General section, then click Configuration Parameters
3. Set the "ctkEnabled" value to false
4. Set the all of the "scsi0:x.ctkEnabled" values to false
5. Open the source folder via Datastore Browser and delete any -CTK.VMDK files
6. Power the VM on
7. Rerun Backup or Replication job to re-enable CBT

I am just wondering why the change and what now changes "ctkEnabled" and "scsi0:x.ctkEnabled" to true again? If it is not done manually during the second power down.

Thanks

[foggy]

Alan, CBT is enabled automatically during the next job run (if it is enabled in the job settings). So those steps appear to be not necessary.