Proxmox node are missing after a reboot.

[fafa24]

Support case ID: 07913147

Hi,

On Saturday, I updated from VBR 12.3.1. Windows to V13. Everything went fine, and I could run backups without issue. On Sunday, there was an issue with a backup job.

No include object was found for c6b62c8b-16b0-30fd-809c-c49d6366ad9c6067c2de-8b49-46aa-881f-45d45d4fb293:135, job: 35b28f81-82e5-418c-830c-254e4b11c75b

I understand that the error message means VBR couldn't find the disk for the Proxmox VM. I tried various things like rescan the Proxmox node and creating a new job without luck.

This environment has two Proxmox nodes and currently only two jobs, and each job backs up only one Proxmox VM.

Later on Sunday, I rebooted the VBR server, and suddenly both Proxmox nodes disappeared from the Backup infrastructure managed servers. I cannot re-add them because the wizard for the virtualization platform does not list Proxmox. I'm aware of KB 4687, the registry is present for the correct port. I already informed support.

Not sure if we can discuss this issue here.

Thanks!

[Dima P.]

Hello fafa24,

Please check the Issue #2 The Veeam Backup Server Certificate is missing the field "Basic Constraints" in the sticky Top Issues topic, the behavior you are describing sounds exactly like the issue with certificates. Thank you!

[fafa24]

Thanks for your reply. According to support they checked Issue 1 and 2 in the log and it is not a problem. However I re-created the certificate and it didn't help.

[Gostev]

Then please open a support case for further troubleshooting.

[fafa24]

A support case is open. I mentioned the ticket number in my initial post.

Support suggested to reinstall the Proxmox plugin, which I did, but with no luck.

[Gostev]

Then just work with them on further troubleshooting. Tell them it did not help and wait for further instructions.

Please note that the forum rules displayed when you click New Topic specifically ask not to bring environment-specific issues to the forum until they are confirmed by our Customer Support to be a product bug,

[fafa24]

Thanks - yes I told them. I thought it is okay to post with the support case ID.

Thanks

[Gostev]

It's fine, we just can't troubleshoot it further over forum posts or really do anything beyond mapping it to the known issues, which Dima has already done.