• The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Remote FTP

rpkemp

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian Web Host Edition Version 18.0.66 Update #2
Hello.

My issue seems possibly related to the one raised in this post from three years ago.

I had both local remote backups running over FTPS without issue for some time, on two separate Plesk virtual servers. When I switched to a new backup server, I couldn't be bothered to fiddle about setting up FTPS so I installed the SFTP Backup plugin on both servers. One of them works fine. But on the other one, while the local backup is stored successfully, I get a nightly email telling me Plesk couldn't connect to the server, and giving the details of the old FTPS backup that I previously set up, but disabled on installing SFTP Backup.

The details of my former backup settings still show up in the FTP(S) Storage Settings page of Backup Manager, but they're greyed out and the option to send backups via FTP(S) is unchecked. Meanwhile, the SFTP Backup details are correct and the option to use it is checked. If I perform a manual backup it works perfectly and the backup file gets transferred to the new backup server. But the scheduled nightly backups all fail.

Any idea why the old backup settings are still present in an active way on the server? Is there a rogue config file somewhere I could edit or delete/recreate?

Thanks in advance.

Rob

Screenshots:

DISABLED FTPS SETTINGS:
plesk_backup1.png

ACTIVE SFTP SETTINGS:
plesk_backup2.png

EMAIL CONTENT:
plesk_backup4.png

SCHEDULED BACKUPS LIST:
plesk_backup5.png
 
Hello, @rpkemp . The behavior you are describing sounds very similar to a Plesk bug identified with ID PPPM-11155, where disabling the remote storage option does not automatically adjust the Scheduled Backup task(s).

Could you please execute the following command on the server and let us know what the output is:

plesk db "select obj_type,repository,active,remoteStorage from BackupsScheduled;"
 
Hello, @rpkemp . The behavior you are describing sounds very similar to a Plesk bug identified with ID PPPM-11155, where disabling the remote storage option does not automatically adjust the Scheduled Backup task(s).

Could you please execute the following command on the server and let us know what the output is:

plesk db "select obj_type,repository,active,remoteStorage from BackupsScheduled;"



Hi. Thanks for replying. This is the output:


Hi. Thanks for replying. This is the output:



+----------+----------------+--------+------------------+
| obj_type | repository | active | remoteStorage |
+----------+----------------+--------+------------------+
| server | local-and-ext | true | ftp |
+----------+----------------+--------+------------------+
 
Thank you. It is a result from the aforementioned bug. Please try the following:

  1. Navigate to Tools & Settings > Backup Manager > Schedule > locate the backup job(s) with "Storage" value set to "FTP(S) storage" and toggle it off.
  2. Then toggle on the backup job(s). The "Storage" value should be updated and the database entry should be updated. You can then disable the backup job(s) in question if they are no longer needed.
Please let me know if that worked out.

Regarding the bug itself, unfortunately, I cannot provide any ETA on when a fix will be introduced. It will be announced in the change log which you may find here.
 
Hi. Thanks. I toggled the backup off and on again, then set it to perform a scheduled backup, and this time it does seem to have worked. Phew!

Many thanks for your help. Hopefully the bug will be resolved before I change my storage settings again ;) - but if not, I know what to do.
 
Back
Top