Resolved Issue with Subscription Backups in Plesk CLI Using FTP Storage

[paolotrombini25]

Server operating system version

CentOS Linux 7.9.2009

Plesk version and microupdate number

18.0.63

We've recently configured backup settings for 94 subscriptions using Plesk CLI, specifically the commands plesk bin scheduled-backup and plesk bin backup-storage. Our goal was to save individual backups for each subscription on an external FTP server, rather than creating a single, large backup of the entire server (which exceeds 200GB). The configuration was applied successfully across all subscriptions.

We scheduled the backups to run at 2:00 AM for all subscriptions.

This morning, when reviewing the backups, we encountered a significant issue. While the 94 backups were correctly created as full backups on the FTP server (since these are the first backups with this system and incremental ones will follow), we noticed an unexpected behavior.

When checking a random subscription through Subscriptions > example.com > Backup & Restore, the backup list showed all 94 backups instead of only the one associated with that specific subscription. As a result, the backup list for each subscription is cluttered with backups from other subscriptions.

This creates a major problem because it’s impossible to easily restore the backup for an individual subscription. We now have to manually identify which backup belongs to the selected subscription from the list of 94 backups.

Has anyone else encountered this issue or know how to resolve it?

 

[paolotrombini25]

Looking at the backup logs arrived via email, we notice several errors during the processes:

The strangest error we cannot understand is the following:

<?xml version="1.0"?>

<execution-result log-location="/usr/local/psa/PMM/sessions/2024-09-10-023242.657/migration.result" local-dump-created="true" export-dump-created="true" local-dump-name="clients/elevelhosting/domains/example.com/backup_info_2409100249.xml" export-dump-name="backup_example.com_2409100249.tar" custom-log-file="/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log" status="warnings">

  <object type="Subscription" name="example.com">

    <object type="Extension" name="Plesk DNSSEC">

      <message severity="warning">

        <description>Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: [2024-09-10 03:56:12.160] 15446:66dfa73c26f9d ERR [panel] Can't open custom log file: /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log

PHP Warning: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory; File: /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php, Line: 26



PHP Warning:  fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory in /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php on line 26

[2024-09-10 03:56:13.113] 15446:66dfa73c26f9d ERR [panel] Unable to open the log file '/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log', cancel profile logging: Failed to open the profiling log file: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory

PHP Warning: touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 9



PHP Warning:  touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 9

PHP Warning: chmod(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 10



PHP Warning:  chmod(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 10

PHP Warning: chown(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 11



PHP Warning:  chown(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 11

"/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log" cannot be opened with mode "a"

</description>

      </message>

    </object>

    <object type="Extension" name="SSL It!">

      <message severity="warning">

        <description>Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: [2024-09-10 03:56:13.662] 15468:66dfa73da17f3 ERR [panel] Can't open custom log file: /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log

PHP Warning: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory; File: /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php, Line: 26



PHP Warning:  fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory in /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php on line 26

[2024-09-10 03:56:13.704] 15468:66dfa73da17f3 ERR [panel] Unable to open the log file '/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log', cancel profile logging: Failed to open the profiling log file: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory

PHP Warning: touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 9



PHP Warning:  touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 9

PHP Warning: chmod(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 10



PHP Warning:  chmod(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 10

PHP Warning: chown(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 11



PHP Warning:  chown(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 11

"/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log" cannot be opened with mode "a"

</description>

      </message>

    </object>

    <object type="Extension" name="Git">

      <message severity="warning">

        <description>Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 3: [2024-09-10 03:56:13.949] 15478:66dfa73de7a2b ERR [panel] Can't open custom log file: /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log

PHP Warning: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory; File: /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php, Line: 26



PHP Warning:  fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory in /usr/local/psa/admin/plib/backup/Agent/Profiling/File.php on line 26

[2024-09-10 03:56:13.991] 15478:66dfa73de7a2b ERR [panel] Unable to open the log file '/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log', cancel profile logging: Failed to open the profiling log file: fopen(/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/profile.log): Failed to open stream: No such file or directory

PHP Warning: touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 9



PHP Warning:  touch(): Unable to create file /var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log because No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 9

PHP Warning: chmod(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 10



PHP Warning:  chmod(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 10

PHP Warning: chown(): No such file or directory; File: /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php, Line: 11



PHP Warning:  chown(): No such file or directory in /usr/local/psa/admin/plib/Plesk/Log/Writer/File.php on line 11

"/var/log/plesk/PMM/backup-2024-09-10-02-32-42-656/backup.log" cannot be opened with mode "a"

</description>

      </message>

    </object>

    

  </object>

</execution-result>

Then we got these error messages:

Restart position accepted (1615191552): Connection to the FTP server has lost

pmm-ras failed (Error code = 1): Import error: Unable to find archive metadata. The archive is not valid Plesk backup or has been created in an unsupported Plesk version

pmm-ras failed (Error code = 1): Curl error: Unable to resume an interrupted download: (13) FTP: unknown PASV reply: Last FTP request: PASV: Last FTP response: 150 Opening BINARY mode data connection for backup_example.it_2409100228.tar (550368185 bytes): Connection to the FTP server has lost

Unable to create the directory: Transport error: Unable to create the directory 'ftps://xx.xx.xx.xx/backup_cli/xx.xx.xx.xx/check1/': Curl error: (21) Quote command returned error: Last FTP request: MKD check1 Last FTP response: 550 Create directory operation failed

Check if you have permissions to create folders in the storage. You can check it independently with the command:

  curl --ftp-create-dirs -v --ftp-pasv --ssl -k -u testuser_cli 'ftp://xx.xx.xx.xx/backup_cli/xx.xx.xx.xx/test-dir/'

Thanks in advance
Paolo

 

[Sebahat.hadzhi]

Hey, Paolo. On the remote FTP server do you have all backup copies of your subscriptions stored in the same folder?

 

[paolotrombini25]

Hey, Paolo. On the remote FTP server do you have all backup copies of your subscriptions stored in the same folder?

Yes, we have set the same path for all subscriptions

 

[Sebahat.hadzhi]

Thanks for the confirmation. Please make sure to define a separate directory for each subscription and you should no longer experience the issue. Let us know if that sorted it.

 

[paolotrombini25]

Thanks for the confirmation. Please make sure to define a separate directory for each subscription and you should no longer experience the issue. Let us know if that sorted it.

Thanks for the solution, after changing the backup path, I now only see the backups associated with the correct subscription in the backup list.

Paolo