been failing intermittently with connection issues.

[Sakila]

Case ID: 05286629
Oracle Linux Server release 6.10
Kernel: 3.8.13-118.44.1.el6uek.x86_64
Agent version: 5.0.2.4567
The computer with multi SAN Storage and iSCSI Disk.

The machine's been failing intermittently with connection issues.
What could be the reason makes the issue? We have been stuck on the issue for around 2 months.

1-1. Only this machine in the same network gets the issue, The backup job was successful rarely when backup the entire computer.
1-2.Veeam Backup Server and
2. It has been successful backing up for a week only backup /dev/sda .
3. Backup job is usually suddenly stuck while backing up.

Thank you for helping.

#Logs removed by Mod

Code: Select all

[08.05.2022 06:53:06.656] <140253466523392>        | 10.0.0.25:2500 connection status: system:111 (Connection refused)
[08.05.2022 06:53:06.656] <140253449737984> alg    | ERR |read: Connection reset by peer
[08.05.2022 06:53:06.656] <140253449737984> alg    | >>  |--tr:Cannot read data from the socket. Requested data size: [13].

logs:
https://drive.google.com/file/d/1qLEXp8 ... sp=sharing

[Mildur]

Hi

Please provide the correct support case ID for this issue, as requested when you click New Topic. I removed the provided Number, because it's not a valid number.
Without case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian

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

[Mildur]

Thanks for the case number. Guessing the issue is difficult in the forums, because we don't know your environment and debug log analysis is done by our support team. They have the tools for that.
From the case notes, it looks like the agent gets stuck and need to be restarted before the service is working again.
Do you have the issue at every job run or only sporadically?

I see in the case also, that it was escalated yesterday by the support engineer. That's the best way to go forward with this technical issue.

[Sakila]

Hi Mildur,
The Backup job is backing the Entire Computer including the Local disk and multi SAN Storage Disk and LUN Disk.

The Job failed on a different type of disk backing Vol Group or SAN Storage or iSCSI Disks while processing the job.
We thought it was because of the IOPS of the target storage, so we change the storage to another one.
I did test only local disk(OS) for a week with success after we change storage to another one.
After 1 week of testing with success only backup OS disk, We change the backup job to the entire computer facing the issue again.

We don't get why the backing job result went back and forth.

Thank you for helping.