Moving templates and their thin based VMs
Hello, I had to free up and reformat a storage domain where I had some templates and many VMs. I was able to move to other existing storage domains disks of VMs created with "Clone" Storage Allocation But some of these VMs had disk with storage allocation of type "Thin" on their related template. So I was both unable to move these templates and VMs disks... I was able to export as OVA the templates and then import again them (with another name "_Copy") on to another storage domain.... then remove VMs and templates and rename templates' names... Are there any chances to better solve these kind of problems if one has to decommission a storage domain? Only export of all VMs and related templates? Is there a way to "consolidate" the disks of an existing "Thin" based storage allocation to Clone? Possibly I can clone the VM? Thanks in advance, Gianluca
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
But some of these VMs had disk with storage allocation of type "Thin" on their related template. So I was both unable to move these templates and VMs disks...
You can copy (rather than move) a template to the new storage domain, then any thin-provisioned disks that rely on the template can be moved. -- Chris Adams <cma@cmadams.net>
On Wed, Apr 21, 2021 at 3:55 PM Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
But some of these VMs had disk with storage allocation of type "Thin" on their related template. So I was both unable to move these templates and VMs disks...
You can copy (rather than move) a template to the new storage domain, then any thin-provisioned disks that rely on the template can be moved.
-- Chris
Thank, Chris! I didn't notice this. So I can select in Storage --> DIsks the disk corresponding to a template, then I see I can copy it to another storage domain. And then the template continues to be one, but in Compute --> Templates select template, DIsks I see now one disk with a "+" sign and expanding it I see the two domains. Great! This means that if I do this I create a break in the dependency of the VM from the particular storage domain, correct? And what if later I go and edit the template, changing its properties? I think they are only metadata that doesn't imply any modification of the disk itself, that is now present in more than one domain, correct? Gianluca
Once upon a time, Gianluca Cecchi <gianluca.cecchi@gmail.com> said:
This means that if I do this I create a break in the dependency of the VM from the particular storage domain, correct?
Yes. I just finished moving some VMs based on templates from one storage domain to another (for some of these, I think this is the third SAN these VMs/templates have lived on, now in the second physical location 5 miles away :) ).
And what if later I go and edit the template, changing its properties? I think they are only metadata that doesn't imply any modification of the disk itself, that is now present in more than one domain, correct?
AFAIK template settings are all in the database on the engine. The disk image on storage is just that: a disk image. -- Chris Adams <cma@cmadams.net>
participants (2)
-
Chris Adams -
Gianluca Cecchi