File Copy Job for configuration failing after upgrade to V13.0.1

[d.artzen]

Hello together,

I just wanted to ask if anyone else has issues with "File Copy Jobs" after upgrading from V12 to V13 on Windows. We use a "File Copy Job" to copy the Veeam configuration backup from the local disk to a hardened repository (since it is not possible to define two locations for the configuration backup). This worked fine up to and including V12.3.2 but since V13 it fails with a "Connection forwarder with ID {7c04b737-d250-4484-a1f4-e9c4eda6dc21} not registered Connection forwarder with ID {7c04b737-d250-4484-a1f4-e9c4eda6dc21} not registered" error. The hardened repo itself is correctly reachable, since our "Backup Copy Jobs" to that repository are all successful.
Support is still investigating (they can see that the VBR can connect, but the session ID created for the data mover agent in the Veeam server was not registered or closed), I just wanted to ask here if I am the only one with such an issue.

Case#: 07895143

Best regards
Daniel

[david.domask]

Hi Daniel,

No issues come to mind at first blush, so please continue with Support on this one.

Out of curiosity, is it a "classic" Hardened Repository from the previous Hardened Repository v2 ISO or did you upgrade to the v13 Hardened Repository from the Veeam Infrastructure Appliance?

[d.artzen]

Hi David,

the hardened repository is a manually installed linux server (Ubuntu 22.02 LTS), at the time we installed that server the Veeam ISO did not exist. And since all other Backup Copy Jobs work fine I don't think it something directly related to it. Especially since in V12 this worked without problems.

[david.domask]

Got it, figured as such but didn't see it confirmed on the case. Please continue with Support, let's see what the investigation turns up. I do advise at some point scheduling the upgrade to the Infrastructure Appliance deployed hardened repository.

[d.artzen]

That will not be possible with our current hardware. The Linux server doesn't have much internal Storage capacity, we had an older QNAP NAS Systems which we attached via iSCSI to the linux server. The connection is a direct network cable from a dedicated interface of the linux server to the NAS. So the NAS is not connected to our network and only reachable through the linux server.
But this config is not supported by the VIA, so we have to stay on the self build system until a hardware refresh.