MENU
Forty days ago, an administrator provisioned a Virtual Machine (vm-01) in preparation for a new project. The project has now been delayed due to budgetary constraints. As part of the monthly service management checks, a second administrator executes the reclaim action on all idle virtual machines and vm-01 is listed. The second administrator accidentally reclaims all idle virtual machines including vm-01.
What action can the administrator complete to prevent this scenario from happening again?
Questions no: 3 Verified Answer = D Comprehensive Detailed Explanation with all VMware Reference = To prevent the accidental reclamation of recently provisioned VMs, the administrator should increase the default value of the 'Exclude VM provisioned in the last x days' setting. This setting determines the period during which newly provisioned VMs are excluded from reclamation analysis. By increasing this value, the administrator can ensure that VMs provisioned for new projects are not inadvertently reclaimed .
Here's why the other options are not the best solution:
A . Create a dynamic group with membership based on vSphere tags so that all new virtual machines are included and then exclude the entire group from reclaim analysis. While this approach can be effective, it requires additional configuration and management of dynamic groups and vSphere tags. Increasing the 'Exclude VM provisioned in the last x days' setting is a simpler and more direct solution.
B . Disable Capacity reclamation on the policy applied to new virtual machines. Disabling capacity reclamation entirely would prevent vRealize Operations from identifying and reclaiming any idle resources on those VMs, which may not be desirable.
C . Create a new policy that disables the capacity reclamation on the policy and apply the policy to the parent object hosting new virtual machines. Similar to option B, this would disable capacity reclamation for all VMs under the parent object, which may be too broad and prevent the reclamation of other idle resources.