You can configure the start and stop order of virtual machines within your vApp. Configure the start and stop order in case you have applications installed in the virtual machines that must start and stop in a particular order.
These settings are useful if you need to start and stop your virtual machines in a particular order. For example, one virtual machine houses a database server, another houses an application server, and the last houses a web server. In order for the related functions to work properly, the database server must start first, the application server must start second, and the web server must start last.
Verify that the vApp is powered off.
- On the Virtual Datacenters dashboard screen, click the card of the virtual data center you want to explore, and select vApps from the left panel.
- Click to view the vApps in a card view.
- In the card of the selected vApp, click Details, and scroll down to the vApp advanced properties.
- Enter the start and stop order properties for each virtual machine, and click Save.
Option Action Start Order Enter the order in which you want the virtual machine to start. You must enter a value for each machine in the sequence. Start Action Select a start action.
The start action determines what happens to a virtual machine when you start the vApp that contains it. By default, this option is set to Power On.
Start Wait Enter the start wait time.
The start wait time is the amount of time you want to wait before you start the next machine in the sequence.
Stop Action Select the stop action.
The stop action is the action the virtual machine takes when you stop the vApp that contains it. If you select Power Off, the VM powers off without performing shutdown actions that ensure stability (which is the equivalent of pulling a plug out of a socket). Select this action if you have not installed VMware Tools. Otherwise, select Shut Down, which ensures stability upon shutting down.
Stop Wait Enter the stop wait time.
The stop wait time is the amount of time to wait before you shut down the next virtual machine in the sequence.