Change tracking target file already exists

After upgrading to VMWare ESXi 5.5 U3 we started seeing random snapshot errors during backups with following message – “An error occurred while saving the snapshot: Change tracking target file already exists.”. Issue is caused by leftover cbt file that is not deleted when snapshot is removed by backup software.

After submitting several logs and traces to VMWare they acknowledged that issue exists and it will be fixed for ESXi 5.5 in June patch release and for ESXi 6.0 in July patch release.

Right now when we detect a problematic VM we browse the datastore and delete the leftover cbt file.

Advertisements

4 thoughts on “Change tracking target file already exists

  1. Hi,

    We are also experiencing this issue and were wondering if you had any further information regarding the expected patch release.

    Also, do you have a reference/case number which I can reference when raising a case with VMware. I assume that the more customers they have linked to it, the higher priority it will be.

    Thanks a lot for any help,

    TG

  2. I’ve noticed the same issue. But only on some of the servers will moving the CBT file and running a consoldation solve the problem. Have you had issues where the CBT file comes back after the consolidation? If so, what did you do to resolve?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s