Backing up a virtual machine with multiple disks fails with the error: Change tracking is not active for disks
search cancel

Backing up a virtual machine with multiple disks fails with the error: Change tracking is not active for disks

book

Article ID: 305224

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Cannot back up the virtual machine with multiple disks using a backup solution, such as Uni trend

  • Backing up a virtual machine with multiple disks using a backup solution, such as Uni trend, fails

  • In /var/log/hostd.log file, you see this error:

    Change tracking is not active for disks

  • In /var/log/hostd.log file, you see an entry similar to:

    Event 6275 : Virtual machine "VM Name" disks consolidated successfully on Host_name in cluster Cluster_name in ha-datacenter.

  • The task and events for the virtual machine (In vCenter Server) displays no error for back up or removing snapshot.
  • In the backup solution logs, you see entries similar to:

    Files to backup:
    FATAL: No backup data received from client.
    Client Name....: localhost.localdomain [127.0.0.1]
    Starting Dir...: Allvolumes:/
    Command-line...: /usr/bp/bin/vprotect/vprotect --server xx.xx.xx.xx --username XXX\administrator --password ******** --backup --UUID 50147225-d893-492e-936b-7e7fee5e8242 --istemplate NO --appaware NO
    Exit Code......: 1
    Exit Status....: Failed
    ----- VProtect Messages ----
    }, 'InvalidArgument' ),
    deviceKey',
    }, 'SoapFault' );
    ----- End VProtect Messages ----
    No client messages due to log level 3
    See client log in /usr/bp/logs.dir/bpserver-0.log
    FATAL: No backup data received from client
    The database update failed. (Attempt 1 of 3)
    The database update failed. (Attempt 2 of 3)
    The database update failed. (Attempt 3 of 3)
    The database update failed. (Attempt 4 of 3)
    Updated: attempt count exceeded. (4 attempts > 3 max attempts specified in Updatedb section of /usr/bp/bpinit/master.ini)
    The database update failed. (Attempt 4 of 3)


  • The ctkEnabled parameter is already true in the virtual machine configuration file.


Environment

VMware vSphere ESXi 5.5

Cause

This issue occurs if the virtual machine has multiple disks and may not have setting ctkEnabled = "TRUE" for individual virtual machine disks (vmdks). As a result, queryChangedDiskAreas for the.vmdks fails.

For example, a virtual machine with two vmdks must have entries similar to:

ctkEnabled = "TRUE"
scsi0:1.ctkEnabled = "TRUE"
scsi0:0.ctkEnabled = "TRUE"



Note: Check the hostd.log files and verify if it has entries such as, Change tracking is not active for disks.


Resolution

To resolve this issue, set ctkEnabled = "TRUE" for all virtual machine disks.

For more information, see Enabling Changed Block Tracking (CBT) on virtual machines (1031873).




Additional Information

Enabling or disabling Changed Block Tracking (CBT) on virtual machines
複数のディスクをもつ仮想マシンをバックアップすると次のエラーで失敗する:Change tracking is not active for disks