Deploying replica fails with .vmdk access errors

A quick post about an annoyance I encountered while recomposing a View Horizon Linked-Clone desktop pool to multiple local datastores. In this situation multiple replicas will be created from the Parent VM.

These replicas are created simultaneously; however during this process the task pane in the vCenter Server shows many .vmdk access errors on the parent VM and as a result replicas are created one after the other.

VMware KB “Deploying multiple virtual machines in VMware vCenter Server 5.x and 6.0.x from the same template fails with the error: vmdk access error (2114026)” explains that this issue occurs because of locked –ctk.vmdk files. These files are part of the Change Block Tracking (CBT) mechanism. The KB provides instructions how to modify the settings of the Parent VM by disabling CBT.

However after editing the .vmx file and deleting the –ctk.vmdk files from the datastore, the files reappeared immediately. To resolve this behavior, SSH to an ESXi host and browse to the datastore where the Parent VM is located.
Then, edit ALL .vmdk files and remove or comment out the line starting with; changeTrackPath=.


2016-04-24-01Figure 1

Now, the –ctk.vmdk files will be gone for good.
To prevent third-party applications from enabling CBT, you can add the following line to the .vmx file of the Parent VM: ctkDisallowed=”true”.
As always, I thank you for reading and welcome your comments.

Advertisements

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

%d bloggers like this: