Welcome to the Community - you can convert the template to a VM and then cold migrate it to the new datastore -
Thanks for you inputs! Below is what I tired with its results:
I tried to move the Template from Datastore using the 'Move to..' feature in Browse Datastore view. While the Template files got moved the actual VMDK files in the templates have enlarged.
My initial template folder size in Browse Datastore view was < 10GB and now after moving template folder to the new Datastore its size has grown to > 30 GB.. The VMDK file has actually enlarged.
Any idea why the VMDK file size has increased?
I do it this way...
Hello, i'm not sure but i think when you have some datastores with two different block size, and if you move VMs between with "Move TO", the migrated VM change to thick formart. This is your case?
Im looking for a cleaner way to replicate a Template Datastore. Right now we have a volume on our test cluster. Its being snapmirrored to our production cluster and our secondary datacenter cluster. We make changes to the test volume, update the snapmirror, and break it off so the other vCenters can see it. It seems that lately we’ve been seeing some weirdness on our hosts and we think it might have to do with this shared datastore solution. We also run into some mounting issues when we update and break the volume. None the less, is this something we can do with VSC? Or something else? We want to utilize VAAI so having the volume on its own NetApp cluster is the only way to do that, so keeping the volume in one NetApp cluster and just presenting it to the vCenters won’t be an option. I’ve read the old Provisioning and Cloning option had some remote mounting options. We’re currently using VSC 6.1