VMware Horizon Community
VirtualSven
Hot Shot
Hot Shot

Update Appstack creates thick copy

In a new App Volumes 2.12.1 environment with vSphere 6.5, I'm experiencing something strange. When I update an Appstack, it usually creates a thin provisioned copy of the original Appstack. But in this new environment it creates a thick provisioned copy of the original Appstack. What can cause this behaviour?

Sven Huisman VMware vExpert 2009-2016 Twitter: @svenh blog: svenhuisman.com
Tags (1)
Reply
0 Kudos
5 Replies
Lakshman
Champion
Champion

Can you share the storage details please. Is it vSAN?

Reply
0 Kudos
VirtualSven
Hot Shot
Hot Shot

No, it's 3-Par. But I think I found the cause. The customer is using an NFS-share on Windows 2012R2 for synchronisation between datastores/datacenters. I think Windows 2012R2 NFS is not a supported storage for vSphere. Only strange thing is that initially the AppStack is thin provisioned. If I update the Appstack before replication has occurred, a thin provisioned clone is created. But if I update the Appstack after it has been replicated to the NFS-share and from the NFS-share to the other datastore, the copied AppStack also becomes thick provisioned.

Sven Huisman VMware vExpert 2009-2016 Twitter: @svenh blog: svenhuisman.com
Reply
0 Kudos
ltonsul
Contributor
Contributor

Has this question been answered. I am using vsan at two sites, with a windows NFS share in the middle. While replicating, my appstacks go from thin to thick on the nfs share, and then thick on the replicated datastore.

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso

You would need to have a different method of copying the disks. If you copy them when using a file browser within VCenter it copies as thin.

Reply
0 Kudos
cliffvmwareeuc
VMware Employee
VMware Employee

If Rays option works please update us..if not we had a similar case last year where there was an appstack copy operation from vSan to NFS and then vSan. It turned out to be default behavior on the copy to the NFS if im not mistaken but it came to be storage related after a test of a NON appstack .vmdk copy operation (Any .vmdk created in vCenter) produced the same issue.

If the same is true for you then i recommend opening a case with vSan for further troubleshooting on this one.

Reply
0 Kudos