- Server operating system version
- Alma 8.10
- Plesk version and microupdate number
- 18.0.72 #3
Backup Manager: A full backup takes hours, during that time period we experience short network connectivity issues to the external FTP storage space. These are probably short, maybe a minute, maybe two. But they are long enough that the backup manager thinks, the connectivity is lost and ends the backup with an error.
Example:
This mostly means that hours of hours of backup activity was wasted, because the backup cannot be resumed.
I am looking for a way to extend the time period that the backup scripts wait to retry the connection, and also would like to increase the number of retries before the backup quits with an "error" message. How can that be tweaked?
Example:
Code:
Unable to create the remote backup: Unable to resume an interrupted upload. It seems like FTP server deleted the file, when the connection was lost. Try to repeat or perform upload manually: The connectivity problem: (55) Failed sending data to the peer: The last FTP request: STOR backup_2509302331.tar: The last FTP response: 150 Using transfer connection
This mostly means that hours of hours of backup activity was wasted, because the backup cannot be resumed.
I am looking for a way to extend the time period that the backup scripts wait to retry the connection, and also would like to increase the number of retries before the backup quits with an "error" message. How can that be tweaked?