7.4

Table 3‑79. Action Menu Commands (Continued)
Action Resource Type Description
Destroy Cloud Machine, Deployment, Virtual
Machine, and NSX Edge
Immediately destroy a provisioned resource. You
must run this action to destroy XaaS resources,
even if they are part of a deployment you are
destroying. Other resources are destroyed when
their lease or their archival period ends.
Except for XaaS, destroying components of a
deployment is not a best practice. Use the scale in
action to reduce the number of machines in your
deployment, or destroy the entire deployment.
The Destroy action is not available for the
following deployment situations:
n
physical machine deployments
n
deployments with an NSX existing network or
NSX existing security resource
n
deployments with an NSX on-demand load
balancer resource
Because an NSX load balancer belongs to an
NSX edge, when an NSX edge is destroyed, the
load balancer resource is also destroyed and
resources are released. When a machine tier that
is load balanced is destroyed, it is removed from
the load balancer pool on the respective NSX
edge.
Note The Destroy action may return a success
message even if it cannot remove a machine
deployment from its endpoint, for example if a
vSphere machine is on a non-vSAN datastore and
its .vmx file contains corrupted or otherwise invalid
data. You should check the request log for
additional information even if the Destroy
message indicates success. Force-destroying a
machine in this state might leave it running on the
endpoint and cause IP conflicts. If the corruption is
corrected on the endpoint (outside of
vRealize Automation), you can retry the Destroy
action.
Business group administrators can choose to
force destroy a deployment after a failed destroy
request. Force destroy instructs
vRealize Automation to ignore failures to destroy
Configuring vRealize Automation
VMware, Inc. 593