Loading...
Loading...
Virtual machines (VM) with a status of Not Detected are in the backups of protection policies. Backups may fail with an ABV0040 error and the following message: VM Proxy BackupJobSession failed -- Unable to find virtual machine with MORef 'vm-5456'. Virtual machine does not exist with MORef 'vm-5456': ServerFaultCode: The object 'vim.VirtualMachine:vm-5456' has already been deleted or has not been completely created The VM mentioned in the error is part of a Dynamic Protection Policy but might not exist in vSphere. The VM asset status is marked as Not Detected after discovery, and the VM remains in the protection policy.
In PowerProtect Data Manager 19.17 and earlier versions, backups would not run for Not Detected VMs. This caused a risk of data loss because the Not Detected status could occur unexpectedly and temporarily. If backups did not run for VM that had been changed to Not Detected , there was no indication that would draw attention to the situation so it could be corrected. In PowerProtect Data Manager 19.18, the behavior for Not Detected VMs was changed so that backups run on the VM. Attempting to back up these VMs, caused a notification that the VM is now in a Not Detected state, allowing it to be corrected in order to prevent potential data loss. When upgrading to 19.18, if there are several VMs in a Not Detected state, backups run against them and alerts are generated. VMs can move to a Not Detected state during removal from vSphere. VM deletion events should be received from vSphere as part of the discovery process. However, sometimes the deletion event can be missed. If this happens, the next discovery sets the state of the VM status to Not Detected .
The following procedure sets the behavior for Not Detected VMs back to being silently excluded from backups. Caution: If the Not Detected state is temporarily or wrongly reported, this could result in data loss. Be fully aware of this risk before making any changes. Run the following commands from the PowerProtect Data Manager server: Set the "token" variable: token=`curl -skX POST https://ppdm01:8443/api/v2/login -d '{"username":"admin","password":"XXXXXX"}' -H "Content-Type: application/json" | json_pp | grep access_token |cut -d "\"" -f4` Then issue a "GET": curl -k --request GET --url https://ppdmprod.lab.local:8443/api/v2/common-settings/JOB_INTERVENTION_SETTING --header "authorization: $token" | json_pp Save the payload to a json file: 'payload.json' { "properties": [ { "name": "noProtectJobForNotDetectedAssetTypes", "type": "LIST", "value": "VMWARE_VIRTUAL_MACHINE" } ]} Issue a "PUT" request to update the field: curl -k --request PUT --url https://ppdmprod.lab.local:8443/api/v2/common-settings/JOB_INTERVENTION_SETTING --header "authorization: $token" -H "Content-Type: application/json" -d @payload.json Then do a "GET" to confirm the change: curl -k --request GET --url https://ppdmprod.lab.local:8443/api/v2/common-settings/JOB_INTERVENTION_SETTING --header "authorization: $token" | json_pp
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.