Replication error

[jorgefavre]

A new VEEAM B&R 9.5 up4 server was installed, in three replica jobs it throws the following error:
"input string was not in a correct format" Could you give me a hand with this error

[Mildur]

Hello Jorge,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

Please update your environment to V11 or higher. VEEAM B&R 9.5 up4 is end of life and not supported anymore. The issue may already be solved in newer versions.
Here you can find our product lifecycle: https://www.veeam.com/product-lifecycle.html

Best regards,
Fabian

PS: support can only help if you upload logs https://www.veeam.com/kb1832

[jorgefavre]

Thanks Fabian.
I am new to the forum, and with veeam B&R, how can I get the ID to pass to them. and where should I upload the logs?

[Gostev]

veeam.com > Support > Open a case

[jorgefavre]

Thanks for the help

[jorgefavre]

Reviewing logs, I found the error.
Does anyone have an idea where to start to solve the problem?

[MOD]
1) Debug logs have been removed per forum rules (already shared with you once before, kindly do read them).
2) This is not a support forum for environment-specific issues, please work with our Customer Support directly.

[jorgefavre]

Dear, good afternoon, well after a long journey I have managed to reach the end of this problem.
As a boss I had said, "NO is also an answer."
The question is the following, after reviewing the logs of the failed jobs, reading from several places, and comparing logs, and MV configuration files, I came to the following conclusion:
This bug:
Processing XXXXXX Error: Input string was not in a correct format.
It is not due to, as they say in several blogs, the date format (at least not in this case).
Reviewing the jobs log I found the following:

Info Enumerating VM disks and driver ports.
Info Getting PCI bridge address.
Error Failed to analyze 'sata0:0'
Error Input string was not in a correct format. (System.FormatException)
Error at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
Error at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
Error at Veeam.Backup.Core.CViVmDisks.GetBridgePciAddress(UInt32 pciSlotNumber)
Error at Veeam.Backup.Core.CViVmDisks.GetSataDisks()
Info 0 SATA disks was found


and there is the key, veeam 9.5u4 does not recognize the string that identifies the pcibridge, or the way in which VMware presents it in the *.vmx file.
As you mentioned, this happens with a VM created in VMware 8.0 and later, with a VM created in Vcente 8 but with compatibility with esxi7u3, the replica works well.

This a priori occurs because this version of veeam is no longer compatible (per data sheet) with vmware 8.
Now, backups are carried out without problems since the methodology used is different from that of replicas.

I clarify all this arises practically experimentally, so if anyone wants to provide any technical/theoretical data it would be appreciated.
The truth is that this was the first complex problem that arose for me and I think the last one that I managed to understand on this learning path as a sysadmin

Greetings

[Mildur]

Hi Jorge

Thank you for sharing. I assume you have updated your backup server to the most recent version to solve the issue?
If you are running vSphere 8.0, then you need to update to a compatible version of Veeam Backup & Replication.
Veeam 9.5u4 is just too old.

Best,
Fabian