Cannot find local Host

[Gerbrand]

I am running a few jobs in Veeam B&R, this is a job that is stored locally and is cloned to send it to the cloud. I did the same with other jobs and they are being backupped to the cloud. This Job worked before but stopped working with this error:

Error: Unable to convert host Id from service provider database to host Id from local database: cannot find local host
BS-EX01 Error 09:49:30 09:49:48 0,0 B 0,0 B 0,0 B 0:00:18 Job has failed. See logs for details.

I have the felling that I miss something very stupid, but all the settings are the same as the local job, and similar to another cloud job.


What does this error mean? Where can I find the log that tells me what's wrong?

[Mike Resseler]

Logging is describe here (including locations): https://helpcenter.veeam.com/docs/backu ... tml?ver=95

But in this case, I would advise you to create a support call. Post the support case ID here and the follow-up after investigation of support engineers

Thanks
Mike

[Gerbrand]

[ID# 02189840] is the support case ID

[Gerbrand]

the problem is solved;

There was a DNS-issue.
What I did, with support from the veeam support

1: Disable the problem job
2: Rescan the cloud repository
3: edit the problem job, with map back-up, and choose the folders name (of problem job)
4: pressed ok and finish
4: run the job.
5: re-enable the job.

[Mike Resseler]

Great news Gerbrand!

Glad it is solved. And thanks for giving us the procedure! Probably will help many people on our forums also!

Thanks
Mike

[Ensposito]

Hey Gerbrand, testing this out now - I had the same issue. Didn't fix mine. I will get a case started.

[Daithi]

I'm having the same issue here. The backup copy worked fine until the server was shutdown and started up again.

"Error: Unable to convert host Id from service provider database to host Id from local database: cannot find local host"

I've logged a support call but if anyone found a different solution it would be appreciated.

[ben.laroche]

If Gerbrand's steps don't work, ensure you have both forward and reverse DNS lookup working (test nslookup with both the name and IP address) of your VMHost. Then, after adding in/fixing the entries, follow Gerbrands steps again, it should work.

[s_t]

the 5-step-solution above did not work for one of our customers, but the solution from Paolo Valsecchi worked - it includes a temporary metadata rename in the CloudConnect repository

https://nolabnoparty.com/en/veeam-cloud ... t-host-id/

[Mike Resseler]

Thanks Sebastian for this additional information.

And thanks to Paolo for writing it out in a blog

Much appreciated all
Cheers
Mike

[ryan1cf]

This solution fixed my issue too: https://nolabnoparty.com/en/veeam-cloud ... t-host-id/
To sum up:
Disabled cloud job
On your cloud (provider) side, rename the .vbm to old.vbm
Rescan the cloud repo from your client (tenant) side
Edit job and re-map the cloud job
Enable the cloud job