i'm currenty testing in my vSphere 7 environment VVOL's. I have installed the Virtual Storage Console 9.7.1 on a local datastore of my host.
But where to place the vCenter Server?
Here i got different informations about placing on a VVOL, someone told me that should be no problem, others tole me that isn't supported, or only not recommended.
Fact is, even if the vCenter Server isn't running, i can power on VM's on the ESXi Host directly. So for only powering on VM's the vCenter isn't needed.
Last weekend i updated my single controller NetApp to 9.7P8 and all was powered off.
First i tryed to power on the VSC, but when the VSC don't reach the vCenter it cames with the wizard to configure a vcenter connection.
When the VSC is running, it don't need the vCenter to power on VM's, but i can't start the VSC without a vCenter. If the vCenter is on a VVOL i got a chicken egg problem... In this case a vCenter can't be on a VVOL.
But my question now, is this correct? Why can't a already configured VSC start the services and connect later to a vCenter when is came available?
The VASA Provider has a internal database and cache the informations he got from the vCenter, must be, because i can shutdown, power off, reove the vCenter from inventory of the host, add it to the inventory and power on the vCenter again without problems, when the vCenter in on a VVOL and the VASA is still running.
The VASA is getting informations like profiles from the vCenter and perhaps a inventory. All other actions mut be done directly with the ESXi host.
During this case i asked the supporter regarding the VSC boot behavior and he told me that the vCenter must be available for a fully function VASA provider. This is a normal behavior, because the VSC is a virutal appliance...
And i also talked to a VMware specialist from NetApp and he was wondering about this behavior too, in his view this behavior was in the past different.
In my view there is little design problem, why not booting the VASA with the last cached informations and wait for the vCenter connection.
O.k. this scenario will be happen very rarely, that all will be powered off, but if so it can be a large problem...
You are correct you don't mix mgmt VMs with vVols. You leave them on traditional storage. NetApp is the only storage vendor using a VM for their VASA while all others integrate that logic to their controllers. Why? NetApp believes it is more scalable. A while back, I noticed also the appliance is requiering vCenter to start all services.
I never implemented vVols in productions, too many drawbacks (not compatible with snapmirror) or missing. It is supposed to be all solved now but still they aren't hight in VMware HCL for vVols.