Object VM name not found

-
Backup Technology: VEEAM


ISSUE: Job fails with the following error message, “Task failed Error: Object <vmname> not found”

Check the log file for the following entries:

Error    Failed to expand object added to the job. Object: 'Object, id: , name: <vmname>, type: VM, vi type: VirtualMachine, host name: ’.
Error    Object <vmname> not found. (System.Exception)

The most direct resolution can be verified by editing the job, selecting the “Virtual Machines” tab, then selecting recalculate. Below is the screenshot for the same.

If any VM whose size comes back as “Not Available”, one should attempt the below as a resolution.


Cause:
This error is caused by the VM’s unique inventory reference identification number (MOREF, or Managed Object Reference) changing within the virtual infrastructure, or the VM having been deleted. Veeam is still attempting to find the VM by its old reference ID number based on a “find vm by NAME where REFID = X” query.

Note: The most common events that cause a VM MOREF ID to change are:
  • Reinstallation or creation of a new vCenter server where the old VC database is not reused.
  • A VM is removed from inventory and then added back to inventory.
  • In rare cases a host crash, which prompts the host to be removed and added back to the VC may cause the VMs on that host get new MOREF IDs.
​
Solution:

Go to the Backup Infrastructure and rescan the vCenter Server.

Remove and re-add VMs affected by this behavior back to the job.

Please note that in version of Veeam Backup & Replication 6.1 and newer, the console session caches the Ref-IDs to make navigation faster. If the Ref-IDs have recently changed, the cache will most likely not have the correct Ref-IDs. To force the Ref-ID cache to be flushed, press the “Add” button and then click the refresh button within the “Add Objects” dialog.










After you have flushed the cache, proceed to re-add the VMs to the job.

After you have added the VMs back to the job, click Finish. Then, open the job once more and repeat the “Recalculate” action.

All VMs should now correctly report their sizes and processes with this will now proceed in your Backup or Replication job.


Comments

  1. AnonymousApril 27, 2022 at 9:09 AM

    Object Vm Name Not Found >>>>> Download Now

    >>>>> Download Full

    Object Vm Name Not Found >>>>> Download LINK

    >>>>> Download Now

    Object Vm Name Not Found >>>>> Download Full

    >>>>> Download LINK By

    ReplyDelete

Post a Comment

Popular posts from this blog

Veeam Guest Agent is not started

-
Backup Technology: - Veeam Issue: - Veeam job failed with below error message. ------------------- VMware Tools are not running. Guest processing skipped. Failed to prepare guest for hot backup. Error: Veeam Guest Agent is not started ------------------- Cause :- -        VM might be rebooted or down during backup job running. -        Veeam run time agent service stuck on VM server. -        VSS writers might be in failed status. Solution :- 1. Login to the effected VM and verity the uptime. If the VM is rebooted during backup job running then it will completed successfully in next retry attempt or next run. or 2. If you found any VSS writers are in failed status then reboot the server to resolve VSS writers issue. or 3. If Veeam run time agent service “VeeamVssSupport” stuck or not deleted after the veeam job completed then you need to delete the service manually or reboot the server.
Read more

VeeamVssSupport Service not found

-
Backup Technology:- VEEAM Issue: - Backup job failed with below error message. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Vvv Cause: - The VeeamVssSupport service cannot be installed because it was never uninstalled. It was marked for deletion instead of being deleted. It cannot be removed, but will be removed automatically when the guest OS reboots. Typically this is due to one of the following programs being open at the time the deletion command w
Read more

Veem job Failed to prepare guest for freeze, wait timeout 900 sec

-
Backup Technology: Veeam Sometimes Veeam backup jobs failed on VM with below error message continuously. Failed to prepare guest for host backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec We need to follow the below steps to resolve the issue. Cause: This issue typically involves a very active transactional application running in the virtual machine, and it is taking longer than expected per the default timeout to freeze the I/O for this application/VM Solution You can change this timeout by modifying the value in the registry of the server where Veeam Backup & Replication is installed as follows: 1.        Go to Veeam registry path HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication. 2.        Add a DWORD (32-bit) value named VssPreparationTimeout. The value is in milliseconds (decimal), the default timeout is 900000, which equa
Read more