Articles in this section

See more

FTP backup fails: Cannot create a file when that file already exists

Avatar
Robert Asilbekov
Updated
Follow
kb: fixed kb: bug ABT: Group A Plesk Obsidian for Linux Plesk Obsidian for Windows

Applicable to:

  • Plesk Obsidian for Linux
  • Plesk Obsidian for Windows

Symptoms

  • FTP backup creation failed with one of the following errors:

    PLESK_ERROR: Error: Unable to export backup: Transport error: Unable to create the directory 'ftp://ftp.domain.tld/Backup/example.com/': Curl error: (21) Quote command returned error: Last FTP request: MKD example.com Last FTP response: 550 Cannot create a file when that file already exists.

    PLESK_ERROR: Unable to create remote backup. Error: Unable to export backup: Transport error: Unable to create the directory 'ftp://203.0.113.2/backup': Curl error: (21) Quote command returned error: Last FTP request: MKD backup Last FTP response: 550 Directory already exists

    PLESK_ERROR: Unable to create remote backup. Error: Unable to export backup: Transport error: Unable to create the directory 'ftp://203.0.113.2/backup': Curl error: (21) Quote command returned error: Last FTP request: MKD backup Last FTP response: 550 Can't create directory: File exists

    PLESK_WARN: Unable to create remote backup, the local backup will be created. Error: Unable to export backup: Repository error: Unable to create the destination directory

    PLESK_WARN: Unable to find base backup for creation of incremental one, the full backup will be created. Error: Failed to exec pmm-ras: Curl error: Unable to resume an interrupted download: (28) Timeout was reached: Last FTP request: RETR

  • Use passive mode option is enabled for FTP server in Tools & Settings > Backup Manager > Remote Storage Settings

Cause

Product issue:

  • #PPP-46305 "Creating an incremental backup in the FTP storage no longer fails."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

Please consider updating your server:


Or:

If update is not possible for some reason you may try the following

For Linux

  1. Connect to the server via SSH/RDP.

  2. Create a backup for cuBackupAgent.php file:

    # cp -ap /usr/local/psa/admin/plib/api-common/cuBackupAgent.php{,.bkp}

  3. Download the custom cuBackupAgent.php file:

    # wget https://plesk.zendesk.com/hc/article_attachments/360006728119/cuBackupAgent.zip

  4. Unzip it and replace the original file

    # unzip ./cuBackupAgent.zip
    # mv ./cuBackupAgent.php /usr/local/psa/admin/plib/api-common/cuBackupAgent.php

For Windows

  1. Connect to the server via RDP

  2. Download the file cuBackupAgent.zip

  3. Unzip the content of the file cuBackupAgent.zip

  4. Back up the following file %plesk_dir%\admin\plib\api-common\cuBackupAgent.php

  5. Place the new cuBackupAgent.php extracted in Step 3 to the %plesk_dir%\admin\plib\api-common\ folder.

Comments

8 comments

Sort by Date Votes
  • Avatar
    Steve

    Replacing cuBackupAgent.php did not work for me. Backups are still failing with the "Directory already exists" error.

    0
    Comment actions Permalink
  • Avatar
    Luca Krebs

    Unable to find base backup for creation of incremental one, the full backup will be created. Error: Failed to exec pmm-ras: Repository error: Unable to extract index from packed dump

    That's the warning we get.

    • Plesk 18.0.23
    • Ubuntu 18.04.3 LTS‬
    • Using FTP(S) storage
    • No passive mode
    • Using FTPS

    Password Protection is enabled and set.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Robert

    Usually, this is caused by connectivity issues between Plesk server and remote backup storage.

    However, I would recommend creating a support request to take a closer look. 

    0
    Comment actions Permalink
  • Avatar
    Christian Serafino

    Great, it work !!!

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Claus Siebeneicher and Steve

    This bug was recently fixed and should be available in the next Plesk Obsidian update. The article will be updated after the fix release.

    The corresponding information will be added here: https://docs.plesk.com/release-notes/obsidian/change-log/

    I confirm that "550 Create directory operation failed" may also be a symptom of this bug.

     

    In case the issue would remain the same after the update, consider submitting a support request: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

    0
    Comment actions Permalink
  • Avatar
    Robert

    Since about a week i get 

    The following error occurred during the scheduled backup process:

     

    Export error: Size of volume backup_asset-trade.net_2004240300.tar 6679319552 does not match expected one 6687988985. The remote backup may not be restored.; Unable to validate the remote backup. It may not be restored. Error: Unable to extract dump header

    Already added tick to use PAssive mode, no change.

    PLEASE Help as is from PLESK update

    Im using  Plesk Obsidian 18.0.26 , Ubuntu 18 lts

    0
    Comment actions Permalink
  • Avatar
    Alexey Lapshin

    Hello @Luca

    Please submit ticket to us to investigate the issue further.
    https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

    0
    Comment actions Permalink
  • Avatar
    Claus Siebeneicher

    Thank you for the quick fix. Helped for the domain backups. However, I have seen s slightly different error message but with the same effect:

    Unable to create remote backup. Error: Unable to export backup: Transport error: Unable to create the directory 'ftps://XXX.XXX/files/EXISTINGDIRECTORY/': Curl error: (21) Quote command returned error: Last FTP request: MKD EXISTINGDIRECTORY Last FTP response: 550 Create directory operation failed.

    There seems to be a difference between the remote FTP Backup Manager scripts for the domains and the plesk system. The scheduled FTP backups of plesk  (tools&settings-> backup manager) were working before and not affected. 

    Remark: The aforementioned update is working but the directory at the remote backup system must already exists, it will not be created if not.

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles