NoDowt
Contributor
Contributor

Storage vmotion of Full Clone desktops

Jump to solution

Hi All,

As I understand, you cannot storage vmotion Linked-Clone VM's & instead move them via a rebalance task... However, what about Full Clone VM pools? I'm thinking they'd be fine, but haven't found anything to confirm this.

I need to move a few Full Clone VM's to a new datastore for maintenance purposes this weekend.

Cheers

Jason

0 Kudos
1 Solution

Accepted Solutions
BenFB
Virtuoso
Virtuoso

Full clones can be safely storage vMotion.

Configuring the vSphere Environment for View Composer

Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.

Note:

Storage vMotion is not supported for linked-clone desktops.

Migrate Linked-Clone Virtual Machines to Another Datastore

Note:

Do not use vSphere Client or vCenter Server to migrate or manage linked-clone virtual machines. Do not use Storage vMotion to migrate linked-clone virtual machines to other datastores.

View solution in original post

0 Kudos
11 Replies
BenFB
Virtuoso
Virtuoso

Full clones can be safely storage vMotion.

Configuring the vSphere Environment for View Composer

Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.

Note:

Storage vMotion is not supported for linked-clone desktops.

Migrate Linked-Clone Virtual Machines to Another Datastore

Note:

Do not use vSphere Client or vCenter Server to migrate or manage linked-clone virtual machines. Do not use Storage vMotion to migrate linked-clone virtual machines to other datastores.

0 Kudos
rnapiza
Enthusiast
Enthusiast

I'm in the same situation, where I need to convert linked clones to full clones, ideally, with no downtime.

I've seen articles where we can clone them.

However, can we storage vmotion linked clones to another datastore.  This would be going to manual full clone pool.

0 Kudos
sjesse
Leadership
Leadership

You can't move the linked clones in anyway to another datastore without causing problems. I just had to do this with around 100 linked clones. The only option I was aware of was to create a manual pool, shut down a linked clone, clone it to a new vm, start it, remove it from the domain, add it to the domain using the new name, and then add it to the manual pool. It was about 20 minutes of download per desktop for me over a few weeks.

0 Kudos
rnapiza
Enthusiast
Enthusiast

Thanks for that.. What kind of problems would it cause? 

0 Kudos
sjesse
Leadership
Leadership

The composer service, the one that made the linked clones, tracks every aspect of where the vm is. If you move anything it will go in an error state and be inaccessible.

0 Kudos
rnapiza
Enthusiast
Enthusiast

hmm.. our goal is to not use the linked clone anymore, as long as that VM is accessible as full clone in a manual pool.

Would the remaining linked clones be affected or just the one being moved?

0 Kudos
sjesse
Leadership
Leadership

That why you clone all the linked clones to full clones, and then add them to the manual pool, then you can just delete the linked clone pool and information those desktops is still intact.

0 Kudos
rnapiza
Enthusiast
Enthusiast

was hoping to use sVmotion to save a few steps and reduce downtime

0 Kudos
BenFB
Virtuoso
Virtuoso

You can't storage vMotion since the linked clone disk has a reference to the replica (You can see this in the descriptor file. Reads come off the replica and writes go to the delta disk). You must do a clone.

0 Kudos
bjohn
Enthusiast
Enthusiast

Is cloning a linked clone to a full clone even supported?

0 Kudos