Errors during backup creation on an external FTP server: Curl error: (55) Failed sending data to the peer: APPE backup

Follow

Comments

15 comments

  • Avatar
    Johannes Hartmann

    If anyone has Problems with uploading large Backups heres a Workaround that is working in my case (after trying everything I found). 

    My Setup ist Plesk Onyx (worked on several previous Versions) 

    Version 17.8.11 Update #21 on 
     

    Ubuntu 14.04.5 LTS

     

    I upload the Backups to a fairly High End FTP only Backupserver and had the same Problems until I started to split it over several disks (excuse me if it's not the right translation of the option, you will find it after you set the location where the Backups should be stored). 

    I used the standard 1024MB and it works like a charm for around 1 Month now, the original Size was ca. 600GB that I had to upload manually after splitting it works without manual work.

    Hope it helps someone until Parallels finds a fix. 

       

     

    1
    Comment actions Permalink
  • Avatar
    Marco Marsala

    Yes, I get FTP upload errors every day. On three servers, I never saw the FTP upload working a single time in many years. Please note that my backup files are 145 GB in size and the FTP service is provided by Livedrive. With smaller backups works without issues.

    1
    Comment actions Permalink
  • Avatar
    Mario Rossi

    Archiving files on the local machine is not "backup". Until this bug is fixed, you should remove "backup" from feature list of products you sell, because this is not backup.

    1
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    Hello @Andy Pedropaulo,

    Thank you for clarification.

    The mentioned warning is the general one, so to find more information about the cause of such behavior it is required to click on View the log:

    The backup Sept 28, 2017 10:18 AM was created and can be restored, although some minor issues occurred. Download the log file View the log

    Once it is clicked, you will see the exact warning and cause of the issue.

    Also you may find more information in /var/log/plesk/PMM/backup-TIME_STAMP/migration.log file.

    In case if any unique error is found, please create a request to Plesk Technical Support: How to submit a request to Plesk support?

    0
    Comment actions Permalink
  • Avatar
    Konstantin Annikov

    @Marco Marsala

    What error do you see in the Backup Manager? 

    Post it here, maybe we have a fast solution. 

    If no, you can always create a ticket for our support here: 

    https://support.plesk.com/hc/en-us/requests/new

    0
    Comment actions Permalink
  • Avatar
    Johannes Hartmann

    Yes, exactly, I use 1024MB, it slows down your restore process but it works. At least for me on Ubuntu 16 and 18.

    0
    Comment actions Permalink
  • Avatar
    Vladimir Chernikov

    Hello @Johannes Hartmann,

    >> Have you tried splitting the backups?

    Thank you for sharing your user experience.

    Could you please share more information about splitting backups. Did you mean using the multivolume backup option in Plesk?

    0
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    Hello @Johannes Hartmann,

    Thank you for sharing the information!

    0
    Comment actions Permalink
  • Avatar
    Johannes Hartmann

    @Andy Pedropualo

    Have you tried splitting the backups? It worked for my servers (Ubuntu 16lts newest only) and is a temporary workaround.

    0
    Comment actions Permalink
  • Avatar
    Konstantin Annikov

    @Mario Rossi

     

    The case is rare one and we met this bug only once. Meanwhile, our developers are working on that issue to confirm the exact reason and fix it.

    In most of cases FTP backup functionality is working as expected.

    Have you faced any errors during backup creation on your environment? 

    0
    Comment actions Permalink
  • Avatar
    Andy Pedropaulo

    This article was updated 8 months ago, I'm using an up to date version of Plesk Onyx 17.8.11 and I still get errors every day on automatic backups of one of the websites hosted by the server. You said it was going to be fixed, apparently it didn't happen.

    0
    Comment actions Permalink
  • Avatar
    Marco Marsala

    This is the error:

    WARNING: () Unable to upload the backup to the FTP storage: Unable to resume an interrupted upload: Seek out of scope of a stream cache (current cache size: 6 MB, required size: 9 MB): The connectivity problem: (55) Failed sending data to the peer: Last FTP request: APPE backup_1710120000.tar13: Last FTP response: 150 Data connection established

    0
    Comment actions Permalink
  • Avatar
    Andy Pedropaulo

    Hi Nikita Nikushkin,

    the warning message I get is exactly the same as the one that is mentioned in the article, with a different date of course:

    "The backup Sept 28, 2017 10:18 AM was created and can be restored, although some minor issues occurred."

    It only happens with a large website, about 40gb.

    @Johannes Hartmann,

    I haven't tried that because I'd rather not split the backup file into lots of smaller files, but I guess I'll give it a try, thanks

    0
    Comment actions Permalink
  • Avatar
    Bulat Tsydenov

    @Marco Please, check the solution from this article, it seems it is the one which describes the issue you have:

    https://support.plesk.com/hc/en-us/articles/115000068645-Error-after-scheduled-backup-task-Hosting-on-domain-example-com-is-skipped-from-backup-due-to-error-ack-Broken-pipe-write 

    0
    Comment actions Permalink
  • Avatar
    Nikita Nikushkin

    Hi @Andy Pedropaulo,

    Indeed, the bug is not fixed yet.

    However, possibly you have a similar error but the cause of the issue differs?

    Could you please send us your error message here? We would like to take a look

    Thx!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request