Since I'm a cheapskate? and trying figure to figure out the benefits of ESXi and figuring out how to reduce downtimes for a server. I had a thought about cutting downtime but I'm not sure if ESXi works the way I hope it does.
So here's the idea:
Have 1 ISSCI SAN to store all the VMs and related files Have 2 ESXi hosts on usb drives connected to it. Setup VM1 on Host1 pointing to VM files on SAN. Duplicate/import VM1 on Host2 pointing to the same VM files. Have VM1 running on Host1.
Assume VMs run some webapp or function as a real server w/all the real server consequences which I accept, ie power failure can cause dataloss, etc.
If I shut down VM1 on Host1, can I start VM1 on Host2 and have it work and function where it left off?
If I pull the plug on Host1 can I start VM1 on Host 2 and have it roughly pick up where it left off?
Has anyone tried this? or have a setup to quickly test this?
Or does anyone know enough about the workings of ESXi to explain what it does to the VM files? ie will the VM files on the SAN be corrupted because ESXi didn't "close" the VMs?
Thanks for the input!
So here's the idea:
Have 1 ISSCI SAN to store all the VMs and related files Have 2 ESXi hosts on usb drives connected to it. Setup VM1 on Host1 pointing to VM files on SAN. Duplicate/import VM1 on Host2 pointing to the same VM files. Have VM1 running on Host1.
Assume VMs run some webapp or function as a real server w/all the real server consequences which I accept, ie power failure can cause dataloss, etc.
If I shut down VM1 on Host1, can I start VM1 on Host2 and have it work and function where it left off?
If I pull the plug on Host1 can I start VM1 on Host 2 and have it roughly pick up where it left off?
Has anyone tried this? or have a setup to quickly test this?
Or does anyone know enough about the workings of ESXi to explain what it does to the VM files? ie will the VM files on the SAN be corrupted because ESXi didn't "close" the VMs?
Thanks for the input!