[BETA] [HPE] Starting Backup, Veeam Bakcup doesn't process

[jisulove]

hi,

after install vme plugin and job created, i started backup job.

but preparing for backup task takes 1 hours over.

https://openbase-my.sharepoint.com/:i:/ ... A?e=Z4fWFZ

why this job doesn't start?

[cody.ault]

Thanks, we'll take a look

[EvgenyBaev]

Hello, jisulove

Does it confirm for several of your VMs or for a particular one?
Would it be possible to reproduce the issue with Debug log level enabled.

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.

Also if you could share backup job logs even on Info level for the currently running job it would be helpful as well. You might need to stop the job for the logs to be generated.
Backup job logs are located here:
C:\ProgramData\Veeam\Backup\Plugins\HPEMORPHEUSVME\Backup

If you have Linux VBR and can provide another instructions about enabling Debug log level and collecting logs.

[jisulove]

my lab environment is VSA linux base backup server.

[vitaliy.yugay]

Hi jesulove,
For VSA the procedure is a bit different:
1. Login to the Host Manager Interface of your VSA with your 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 "Trace", save and import the edited file to the VSA in Host Management Interface

• {...,"Logging":{"LogLevel":"Trace",...},...}

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

Another option is using root shell on your VSA: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
1. Edit and save the "LogLevel" to "Trace" in the config file /etc/veeam/platform-service-hpemorpheusvme/appsettings.json

Code: Select all

sudo nano /etc/veeam/platform-service-hpemorpheusvme/appsettings.json

• {...,"Logging":{"LogLevel":"Trace",...},...}

2. Restart the service

Code: Select all

sudo systemctl restart veeam-platform-service-hpemorpheusvme

After that please confirm the issue again and share the logs bundle. Logs can be downloaded as follows https://helpcenter.veeam.com/docs/vbr/u ... ading-logs

[MrWinsonWolve]

Same thing here.
worker could be deployed without a flaw, but backup job hangs at "Preparing for backup" forever, at least until I restart the Morpheus Veeam service on the Veeam appliance.
* Redeployed workers.
* Tried different VMs (Windows Server 2025 based)

[EvgenyBaev]

Hello, MrWinsonWolve

If the issue is constantly reproduced in your environment collecting logs with Debug level enabled would be extremely helpful for us.
The instructions for Linux VBR and Windows VBR are in the thread.

[vme4tw]

I also have this issue on all VMs that i have tried.

Before i enabled debug logs, the logs just seemed to wait for something. the logs is just filled with:

Code: Select all

{"InstanceId":"80031","CallContext":"80031","Line":"3","Delta":"00:00:00.0014428"}
2026-01-15 08:47:49.6569 00085 [6368] INFO  | [PierEndpoint[5]]: Outgoing call 'System.Threading.Tasks.Task`1[[System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]] IsTaskFinished(System.Guid taskId)' {"InstanceId":"80034","CallContext":"80034","Line":"1"}
2026-01-15 08:47:49.6569 00075 [6368] INFO  | [PierEndpoint[5]]: Outgoing call has completed {"InstanceId":"80034","CallContext":"80034","Line":"3","Delta":"00:00:00.0014315"}

I have enabled debug logs and collected them, where can i upload them?

[vitaliy.yugay]

Hi @vme4tw,
Some additional configuration that was not mentioned in this forum thread is needed. Could you follow these steps please. Cody @cody.ault will reach you out about how you can share logs with us. Thank you in advance!

1. Configure {"BackupRestore": {"BackupTimeout":"7 day"}} to "30 min" in /etc/veeam/platform-service-hpemorpheusvme/appsettings.json similarly how you set Debug LogLevel previously. It should look like this after the change:

Code: Select all

{...,"BackupRestore": {"BackupTimeout":"30 min"},...}

2. Restart the service:

Code: Select all

sudo systemctl restart veeam-platform-service-hpemorpheusvme

3. Run a backup job and wait until it will fail by timeout
4. As soon as your job session is failed, download log bundle and share with us

[vme4tw]

Great.
Im running windows, but it doesnt matter(i suppose)
I have edited the BackupTimeout and ran the backup again (After Veeam HPE Morpheus VME service restart), waited for the timeout, and have a zip file with all the files & folders in C:\ProgramData\Veeam\Backup\Plugins\HPEMORPHEUSVME\ ready for upload to Cody.