vSphere Clustering Service VMs on Veeam NFS datastore


Userlevel 7
Badge +3

As you may know, with vSphere 7 Update 1 VMware introduced the vSphere Clustering Service.
The plan is to get more independent of vCenter Server for certain cluster features like for example DRS.
Where you certainly notice the difference, compared to older releases, are the vCLS agent VMs shown in vCenter.

https://blogs.vmware.com/vsphere/2020/09/vsphere-7-update-1-vsphere-clustering-service-vcls.html

There's no need to backup them and if you have a current Veeam version (v10a Patch 20201202 or higher), they're are automatically excluded from your jobs.
The agent VMs are manged by vCenter and normally you should not need to look after them.
Normally…yesterday we've had the case were some of the vCLS VMs were shown as disconnected; like in this screenshot:

Checking the datastore we have noticed that those agents VM had been deployed to the Veeam vPower NFS datastore.
As this datastore is managed by the Veeam server and can connect/disconnect at any time, it's a very bad location for the vCLS VMs. Unfortunately you can't control the placement of the VMs or hide/mask a datastore, so this could happen anytime.
Searching for similar issues I've only found this post in the VMware Community; so this issue is known but probably also rare:

https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCLS-VMs-datastore-selection/td-p/2837202

 

If this happens to you and you find the VMs disconnected, the solution or workaround is rather simple. Just remove the VMs from the inventory in vCenter with a right-click. A few seconds later a new VM is deployed.


 


8 comments

Userlevel 7
Badge +5

Yes this new feature for v7 is interesting especially how vCenter deploys them.  They are not marked for backup for my lab nor would I back them up since a new one is deployed anytime anything happens.

Great article links and some further reading now. :grinning:

Userlevel 7
Badge +3

@regnor : Interesting, thanks !

Userlevel 7
Badge +6

Thanks @regnor for sharing your finding!

I have to say, VMware has not done itself any favors by enabling this feature in vCenter 7 U1 without an easy option to disable it. I would have preferred to see a opt-in, rather than a complicated opt-out.

Userlevel 7
Badge +3

That’s right @vNote42 Such a change should be well thought and perhaps needs more attention or a transition phase.

By the way it looks like I’ve posted this as a question instead of “content”… @Kseniya Is it possible to change the topic type?:neutral_face:

 

Userlevel 7
Badge +3

Just converted it to ‘content’, @regnor :blush:

Userlevel 7
Badge +3

Just converted it to ‘content’, @regnor :blush:

Thanks Kseniya 😀

Userlevel 7
Badge +3

Great post @regnor !!! Thx for sharing! Love this ;-)

Userlevel 7
Badge +2

Something to be aware of the rare time I need to do recovery processes. Eek! VMware strikes again 🙄

Thanks for sharing @regnor !

Comment