VMware Horizon Community
chriswu11111
Contributor
Contributor

Desktop deployment across multiple datastores

Hi Guys,

I currently have a 3 esxi servers setup. Each with RAID about 1.5TB.

Host 1 = View Manager, Contains Desktop golden image

Host 2 = View Manager replica

Host 3 = Vcenter, Composer

I have just created an automated floating pool on composer and specified to use the datastores located on host 1, 2 and 3 to store the clones. I selected 3 as the number of linked clones to create.

Once it started to provision the 3 desktops it put it all onto HOST 2..............

Now i'm confused i thought it would just create 1 on host 1 then 1 on host 2 and 1 on host 3 just to balance it out.

Is there away to do this? or does View just randomly pick a datastore on its own?

Reply
0 Kudos
6 Replies
mittim12
Immortal
Immortal

Does each host have it's own set of local storage or you using shared storage?  

Reply
0 Kudos
chriswu11111
Contributor
Contributor

Each host has its own local storage.

Reply
0 Kudos
mittim12
Immortal
Immortal

The VM's need to be able to communicate with the replica so if your replica is on two than it's probably just trying to place the clones on the same  datastore so that they work correctly.  There is also a formula for datastore placement.  I'll see if I can locate that so you have a better idea of how View places VMs when using multiple datastores.

Do you have the option to use shared storage?  As it stands now you have some serious points of failure?

Reply
0 Kudos
chriswu11111
Contributor
Contributor

thanks but sadly....we don't....so local storage is the only thing i can do for now.

Any chance you could dig up that info for me please regarding the storage placements thanks?

Reply
0 Kudos
Camek
Enthusiast
Enthusiast

If you specify that View can use more than one storage location for geneated desktops you will find that it places all the generated desktop on the storage location with the most "free" avaiable storage.

Reply
0 Kudos
mittim12
Immortal
Immortal

I can't find a forumla but it seems like it was based on more than just free space.  It also took into account the amount of VMs stored on the datastore before the rebalance.  

Reply
0 Kudos