I've installed the VME Beta Plugin on my Linux VSA. Updated the Console with the new Plugin. My VME Manager is on 8.0.11, so everything should be okay. Added my VME Manager to veeam, created a backup job and deployed(?) a worker. Tried to test the worker and received the following error:
02.12.2025 21:51:55 Succeeded : Testing the worker vme-worker
02.12.2025 21:51:55 Succeeded : Finished searching for uploaded worker VM images
02.12.2025 21:51:55 Failed : Failed to deploy the worker VM: Object reference not set to an instance of an object.
02.12.2025 21:51:55 Failed : Worker vme-worker test failed: Object reference not set to an instance of an object.
Looking at my VME Manager, I can see the uploaded virtual image with a size of 967.9MiB.
After you went through the wizard to add the VME Manager to VBR, did you run through the wizard to deploy the worker to the cluster and test it at that point? From the collected logs, there should be a platform services log in the .\Veeam\Backup\Plugins\HPEMORPHEUSVME folder that might have more information. You could try deploying a new worker as well to see if it reproduces
Could you please also enable the Debug log level before reproducing the issue.
To enable Debug logging:
1) Open the appsettings.json file as administrator.
Location:
C:\Program Files\Veeam\Plugins\HPE Morpheus VM Essentials\Service
2) In the Logging section, set the log level to Debug.
3) Restart the VeeamHpeMorpheusVmeSvc service.
4) Reproduce the issue and collect the log file.
5) Afterwards, you may set the log level back to Info and restart the service again.
Hi Sang Cheung,
Unfortunately, there were no updates for the thread topic for a while.
If you could enable Debug logging, reproduce the issue and share logs with us as described above, it would be helpful for us to proceeding with investigating the issue.
Thank you.
For VSA the procedure to enable Debug logging and collect logs is:
1) Login to the Veeam Host Manager Interface of your VSA with Veeam admin user credentials
2) Navigate to Logs and Services > Host Configuration tab
3) Locate and download a configuration file with the following path: /etc/veeam/platform-service-hpemorpheusvme/appsettings.json
4) Edit the "LogLevel" property to "Debug", save and import the edited file to the VSA in Host Management Interface
{...,"Logging":{"LogLevel":"Debug",...},...}
See more details in VBR 13 User Guide: https://helpcenter.veeam.com/docs/vbr/u ... tion-files
5) Restart the plugin service veeam-platform-service-hpemorpheusvme, see https://helpcenter.veeam.com/docs/vbr/u ... m-services
6) Download and share logs, see https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
sang.cheung wrote: ↑Dec 12, 2025 2:29 am
Hi Cody,
I have sent the logs by email for your checking.
Thanks.
Hi,
We have checked the logs and found that a Group ("site") is not configured for the cluster you are trying to deploy a worker VM. You may see that your cluster lacks a Group in VM Essentials web UI when you open the cluster Summary page. The Group property is required for an instance provisioning in VME in 8.0.11, and our solution determines what Group to use for a worker depending on a cluster where it is getting deployed.
The issue will be surely addressed in the Veeam Plug-In for HPE Morpheus VM Essentials 1.0 release. For now, if possible, you could reconfigure the VME HVM cluster by setting it some Group. You can read more about Groups in VM Essentials user guide https://support.hpe.com/hpesc/public/do ... his-task-1
Hi,
The root cause is not clear from logs on default logging level, but I suspect that it might be similar to the one mentioned in the previous post. Could you check if a target HVM cluster that you configured for the worker VM has a Group set in VM Essentials web UI?
Navigate to Infrastructure > Clusters > {your-cluster} > Summary tab. There you will see your cluster info, including Group that your cluster belongs to.
If the Group is not set for your HVM Cluster, that is our case. If possible, please reconfiguring it to the same Group which is set for the parent Morpheus Cloud (you may need to remove it from the Cloud and add back). Then remove and re-add the VME to VBR backup infrastructure and try worker test once again.