VM-ID shows 2 diffrents ID's ,Why?

[skydok]

Hi,
When doing Backups with Veeam it changes the ref-id of VM because vCenter somehow shows now a new id for the same VM.
When doing trough ESXi vim-cmd vmsvc/getallvms
the VM-ID is "24" .

When doing trough PowerCli Get-vm and checking the ID on the specific VM its 8444
it happend on several VMs also not all. The only thing happend in the enviorment is that 2 ESXi servers have cahnged from
iSCSI to FC and some updates where installed.
I would like to know the mystirous scenario here

Before trying to open a case at VMware , i wanted to know if somebody also saw it ?

[Vitaliy S.]

Hi,

When doing Backups with Veeam it changes the ref-id of VM because vCenter somehow shows now a new id for the same VM.

Can you please clarify your question as I'm not sure I fully understand that? Please be aware that when you register VM in the inventory, it automatically receives a new ID from the vCenter Server.

When doing trough ESXi vim-cmd vmsvc/getallvms

VM has different IDs when looking through vCenter Server and standalone hosts. You might not have vCenter Server installed in your infrastructure, but still VM should be identified somehow, thus it receives the ID from ESXi host as well.

Thanks!

[skydok]

Hi Vitaly,
What of course i understand the ID sections .
I did not re-added to inventory the VM's.It just happend.
For Example:
When i go on Veeam Backup Server to C:\ProgramData\Veeam\Backup\MongoDB which is the job i'm talking about.
Inside is a log of the specific VM which is :
Task.MongoDB.vm-24_1.log
Task.MongoDB.vm-24_2.log
Task.MongoDB.vm-24_3.log

But there is also another new one created called Task.MongoDB.vm-8444.log

The virtual machines didn't changed so therfore its like the Veeam Software sees the VM now no the same way as before,altough the job itself didn't change.

[Vitaliy S.]

Oh, now I see what you're referring to. I have just checked our lab and my backup job has the same IDs for the VMs added to the job. Can you please open the job log itself and search for "VM ref" tag? Do you also have different IDs there?

[skydok]

Sorry for the delay i dind't get the update for this post.
Well the thing is that the job for the newst logs shows the VM-ID 8444 ,if i got back 2 logs of the job
when i saw the change happend i see the VM-ID 24 in the log.

so somthing happend on this day for sure.But i don't know what.

[Vitaliy S.]

Do you have any monitoring solution or Veeam ONE that could tell you the configuration change that happened at that time? If not, then I would wait till this happens again and then investigate the debug logs and vCenter Sever event log.

[skydok]

I don't have a monitoring solution. I spoke again with the customer and they say that "They didn't do anything"
well i can't confirm that.