• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Backup Problems (large files)

clops

Basic Pleskian
I have two servers both running PLESK 8.6 on Debian. One is a live server, second acts as a backup server.
The live servers backs up per domain once per week (@various times to reduce load levels) and this has worked well up until recently, when two of my domains have reached size of over 1 Gb data. These two backup procedures fail over and over again stopping a various points in time. The following error message is generated:

Domain: profipodcast.at
Plesk entry point: https://drum.essentialmind.com:8443/

Following error is occured during scheduled backup process:

Error in UploadToRepositoryState.doActivityRunner()
Traceback (most recent call last):
File "/opt/psa/admin/share/agent_runner/agent_runner.py", line 98, in doActivityRunner
newState = self.doActivity()
File "/opt/psa/admin/share/agent_runner/agent_runner.py", line 428, in doActivity
shutil.copyfileobj(localfh, remotefh)
File "shutil.py", line 25, in copyfileobj
fdst.write(buf)
File "/opt/psa/admin/lib/python/ftputil/ftp_file.py", line 196, in write
self._fo.write(data)
File "socket.py", line 248, in write
self.flush()
File "socket.py", line 235, in flush
self._sock.sendall(buffer)
error: (104, 'Connection reset by peer')

How can I stop this? I have tried setting the backup procedure to split the file into 200Mb chunks -- no joy.

p.s. There are no limitations in HD space whatsoever. Both servers have a RAID1 1TB disk that is just about 2% full.
 
Back
Top