Hi guys anyone could explain or tell us if there is a solution or workaround to this problem:
After adding new datastore (VMFS datastores) on vmware hosts within a dedicated virtual center and view environment, the VDM dashboard does not show this new added datastores.
The desktop pools were made by manual desktop pool and individual assigned virtual machines.
After manual rebalancing the virtual machines up & running by moving those from the old datastore to the new one added, the automated always powered on settings of VDM stop working.
In the VDM logs we found a lot of "error.. could not start desktop XXX for user YYY ...etc etc..
First we thinked that the problem was the storage vmotion. Actually it seems that VDM dosn't start VM in the new datastore becsuse it is not able to see and correctly register those DS.
The only way to make visibility of the new datastore was to restarts all the VDM connection servers.
The automated alway powered on restart of virtual machines started to work again!
Is there anyone with an idea to remediate this issue withou restarting VDM service?
Hi, when you say you "Manually Rebalanced" do you mean you used Storage vMotion rather than the Rebalance feature within View? If this is the case, try and vMotion the VM's back to the datastore that came from and see if you can power them on again.
Never manage your View desktops within vSphere, always manage them within View.
How many Connection Servers do you have in your View Pod? And are you using tunneling or direct connections?
If you have more than one connection server and you are using direct connections, restarting a connection server will not impact the end users. The active View sessions are bypassing the Connection Server and any users that happening to be connecting at the same time as one of the connection servers being down will still be able to access their desktops via one of the other Connection Servers.
2 connection servers. Direct connection. Manual pool with individual virtual machine. The fact is that it was impossible to rebalance due to we haven't an automated pool and there was'nt the command available.
Yes we know that you have to rebalance from the VDM console an not from vsphere. But the question is, why new datastore added weren't available since the VDM restart.
in previous release of View the issue is not present.
So i think vmware, in 5.1.x release including vsphere vcenter server (now from 5.1.0 to 5.1.0a an 5.1.0b) has to work hard to debug some GUI features.
Does all the vSphere hosts see the new datastore? If not then it would explain the behaviour.
yes all the host have full access to the 4 new datastore in full redundant path. The datastores are mounted via iSCSI SW Initiator using a binding with 2 physical nics. No issue and full check up by NetApp virtual storage console.
we stay on