Hi @Lucy ! As you have noticed, we never really ‘forget’ a vm was backed up as part of content, similar to how SQL works. Once we know it is there, it no longer has to be discovered. We’ll just consider it part of the content.
There is a way to control how quickly vms will be considered deconfigured via an Additional Setting here:
Controlling Client Deconfiguration
By default, VM clients are deconfigured 30 days after the VM is no longer included in backups.
-
For virtualization clients that are configured for VM-centric operations, to change the waiting period before a VM client is deconfigured after it is no longer included in backups, configure the NumberOfDaysToKeepUnProtectedVMs additional setting as shown in the following table.
For instructions about adding an additional setting from the CommCell Console, see Adding an Additional Setting from the CommCell Console.
https://documentation.commvault.com/11.26/expert/126639_deleted_or_deconfigured_clients_for_vm_centric_operations.html
However, you’re looking to delete deconfigured vms en masse so they are gone. Let me ask around to see if we have anything handy. I’m sure there are options via Workflows as well.
Hey Lucy, in addition to what Michael mentioned to control the decommissioning for VMs here is the Work Flow and other options you have to retire (and as a result, delete) these VMs:
https://documentation.commvault.com/11.26/expert/91891_server_retirement_workflow.html
https://documentation.commvault.com/11.26/expert/102030_retiring_client.html