Weird issue after upgrading from v12 to v13

[jrbaumann]

Hello,

Upgraded from v12 to v13 2 weeks ago. Everything seemed to be ok, but i noticed that in the Veeam console i'm now seeing, i'll call it a phantom, Exagrid. The phantom Exagrid has a host ip address from a subnet that we used to use prior to moving from one location to another and it no longer exists in our corporate infrastructure. I'm not sure where this came from as it hadn't been in Veeam from Nov.2024 (when we moved locations) until just after this upgrade to v13 a couple weeks ago.

This is an off-domain implementation.

It seems like some of the backups work, but others are seeing errors like this

Warning : Using ******** scale-out repository extent (unable to meet data placement policy) - Most of these jobs will finish

Some will fail with this error

Failed to delete 'xxxxxxx.vbk' per retention policy

Most of the failures were on servers with Windows Agent 13 on them, so i decided to point them to a different SOBR and now they are all working, albeit slow.

The "phantom" Exagrid is listed as "Unavailable" under the backup infrastructure tab, but is listed as part of the SOBR.

Veeam engineer on my case (#07964877) thinks it is DNS related, but changing the hosts file on the server and restarting the Veeam services made no changes.

I've just updated the case again just a bit ago, but was wondering if anyone else had any ideas?


Thank you

[david.domask]

Hi Jeff,

Checked the case, and does not match any known issues at first blush, so please continue with your Support Engineer.

Regrettably we won't be able to meaningfully troubleshoot this one over the forums, and as I get it from the case notes / your description here sounds like the phantom was previously not in the environment but got resurrected after v13 upgrade -- perhaps something in the configuration database that needs to be checked but I'm only guessing.

Regardless, please continue with Veeam Support; if there are concerns on how the case is being handled, use the Talk to a Manager button from the Case Portal and you will be connected to Support Management, who will review the case and allocate additional resources as needed.

[jrbaumann]

Thanks David,

There was a request to send a backup of the database, but for some reason I cannot get the ftp site to connect. Tried from our office and from home and it will not connect. I did comment about this in the ticket. Any known issues regarding the ftp site connectivity?

Jeff

[david.domask]

None that I'm aware of at the moment. Do the normal HTTP uploads not work?

If so, report this to your Support Engineer on the case, they will advise on how to proceed.

[jrbaumann]

OK.

Its nearly 8GB upload so its greater than the website allows.

I did note it in the case on 2.2.26 when i couldn't upload the requested file.