• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

VM dependencies

O

officeboy

n00b
Joined
Sep 28, 2011
Messages
38
Recently started playing with ESXi (4.1 and now 5) and with VSA's (HP P4000, openindiana). One thing that really seems to be a trouble for me is that when shutting down the physical box I always just start shutting down Vm's and forget that most are dependent on one.
Is there a way to make other VM's dependent on one that that is is not able to be shutdown? I realize that in a production environment there would typically be more storage appliances, and your not shutting down for hardware changes on a weekly basis. But seems like you should be able to set a VM as critical and not be able to shut it down first (gah I've done it twice now)
 
Sometimes good labeling is the best way to go. Just rename that VM in your list, put some parenthesis out to the side that tells you NOT to do that ;).
 
You can always set it up in the correct order using the Virtual Machine Startup/Shutdown in the configuration menu in the vsphere client.
 
Vader said:
You can always set it up in the correct order using the Virtual Machine Startup/Shutdown in the configuration menu in the vsphere client.
Click to expand...

I have a nice order set for startup and understand that it will work backwards for shutdown, but how do I trigger an automatic shutdown event from the client?

And I'll look into folders, thanks.
 
If you have vCenter you can use vApps to handle startup and shutdown ordering. I don't recommend the use of them though, unless you're willing to deal with the servers being child members of a resource pool.
 
Vader said:
You can always set it up in the correct order using the Virtual Machine Startup/Shutdown in the configuration menu in the vsphere client.
Click to expand...

Only possible on standalone hosts though unless you "pin" vms to a specific host which is quite pointless when using HA / DRS

defuseme2k said:
If you have vCenter you can use vApps to handle startup and shutdown ordering. I don't recommend the use of them though, unless you're willing to deal with the servers being child members of a resource pool.
Click to expand...

Or just have one resource pool, but I agree, I always try to avoid them unless needed. But in a DRS cluster really the only option ....
 
Only possible on standalone hosts though unless you "pin" vms to a specific host which is quite pointless when using HA / DRS
Click to expand...

He's obviously using one host since he already had it set up.

If he's using HA/DRS then configure restart priorities.
 
Thanks guys. Maybe I'll be able to do more testing with this when I get a few other servers that don't need deployment right away.
 
You must log in or register to reply here.
Back
Top