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
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
Statistics: Posted by jorgefavre — May 15, 2024 9:17 pm
/english-betterindia/media/post_attachments/uploads/2022/05/Sustainable-home-10-1651667432.jpg)
