Table 3-1. Permitted Licensed Operations When the License Server Is Unavailable
Installation and configuration guide....
Can anyone clarify where the HA information/heartbeat control is kept?
I was always under the impression that VC kept control of all of this (DRS/VMOTION as well). So if you lose your VC server then these features would not work.
I did some testing, my vc server was a VM on the host I crashed, and the HA did not kick in as expected.
Hence me wanting some clarification.
I believe the HA module actually uses an engine that VMWare has licensed from Legato called the AAM (Automated Availability Manager).. Previously known as DAS (Distributed Availability Services)
This component has a very high dependency upon fully functional host name resolution. So before you enable VMware HA, check your /etc/hosts file, and your /etc/resolv.conf file to ensure accuracy.
The log file for VMware HA can be found in the service console in the directory
Not in this but it may help..
HA information is stored on each host. VC is not required to keep the heartbeat alive, but it does monitor the process and is required to configure it.
Ahh ok. I knew about the DNS bit, and confirmed that was all working ok sweet. This was on ESX 3.0.0 as well. I might try it again on 3.0.1 and see what happens.
Thanks for the clairfication
AMEN MY BROTHER! THEY NEED TO BRING THE GRAPH BACK!
I'm bringing it back!
I like this idea, a VM as the VC box I can then split out the licence server into a VM too and make use of HA...
Could also take advantage of vmware ESX networking here to give good redundancy on VCS communications.
I'm struggling to think of a situation where this wouldn't work well
VC as a VM is VG (very good). Just make sure you have good backups or your VC DB to tape or some other storage that is seperate from your SAN or NAS or iSCSI or M-I-C-K-E-Y M-O-U-S-E or whatever you use.
Ever feel like we use too many acronyms?
NIMHO...... ROFL....... ok i'll shutup..... ASAP
I think the biggest downside is physiological in that some people do not feel comfortable with their VirtualCenter server being a VM. Although I would say its possible we could see a bug related to running VC in a VM, but so far so good for us.
First get HA working, then test your VC VM and you will see that it works.
We also are running VC 2.01 as a Virtual in a HA cluster with no issues. Trying to push this as the end solution though doesget some resistance which I percieve as Historical Mind set.
In reality while VC is not cluster aware the HA route on external storage has to be seen as a good high availability alternative. It just comes down to how well it scales and the need to ensure you point to a seperate SQL Server (Clustered, Physical) due to the IO nature.
No you have to know the roadmap of vc, because it will change in
future /more i can not say). VC will be cluster aware.
So I designed the vc environment in the following:
One physical server with windows 2003 sp1 enterprise licence for vc in he primary location
and one physical server with windows 2003 sp1 enterprise licence for vc in the secondary location.
The db is on san (global cluster veritas).
The primary server is the hot one and the secondray is the cold one (vc service disabled).
When VC is cluster aware then there is not much work for the infrastructure to do. it is only config.
One advantage is , every time an update for vc comes out,
I can test it on the cold vc server.
Message was edited by:
I don't really see the advantage of your setup vs. running VC in a VM as far as patching goes. Patching can be just as easy with a VM as well, you can use snapshots, or make a clone and test on that.
I have the VC database installed on a physical MSCS cluster (we consolidated several of our DB servers) and the VC app and licensing server in a VM. To me this provides the best mix of high availability, stability, and flexibility, and cost savings.
Anyway, there is more than one solution to this problem.
Same path for us, have HA providing the OS level high availability and the SQL Cluster ensuring the data store. Works for us until the mroe enterprise aware mdoel of VC is around.