The re-scan will reassign the VMs and host IDs to Veeam, and you can rerun the job. Go to the Backup Infrastructure tab find your vCenter and with right mouse click select scan. The solution for this is to re-scan your vCenter or ESXi host where these jobs are connected. Therefore, this error fits perfectly with the root cause. All VMs were migrated to a new Cluster and a new Datastore. That is what was done in the day before in these VMs. I remember from previous errors that this type of issue could happen when you move your VMs to a different Cluster/ESXi host or Storage. This error was encountered inside of all Jobs and all VMs. This week had a strange issue in some particular Backup jobs with the following error : Failed to create processing task for VM – Error: PhysicalHost with id ’16c8ee9c-431e-4de0-945a-55bc5a94eb05′ was not found. While in the air at 10,000 feet will take the free time to write this blog post about Veeam how to fix Error PhysicalHost with id not found.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |