Forwarded to devs After a failed remote backup, the local backup remains in local storage, but the subscriber cannot see it

[Bitpalast]

Username:

TITLE

After a failed remote backup, the local backup remains in local storage, but the subscriber cannot see it

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Centos 7.9, Obsidian with latest MU

PROBLEM DESCRIPTION

The backup defines that in case of a failure in the FTP storage of a backup, a local copy shall be stored. However, if a subscriber creates such a failed backup, a local copy is stored, but the subscriber cannot see that local copy, neither remove it. Only the server admin can see and remove it.

The problem with this is that the admin does not know about such locally stored backups unless he looks through all subscriptions. The subscriber does not know about them either, because he cannot see them. But they occupy space in the subscriber's subscription and are counted against his quota. They are also shows in the "Backups" section of the "Statistics" overview of the subscriber. The subscriber sees a backup occupation in the statistics, but when he opens his backup settings, he does not see any backups (or his remote backups only). This can lead to a situation where the subscription fills up with faulty backups that - for reason of failure - are stored locally.

STEPS TO REPRODUCE

Set general backup settings of the system to "Save backups in the server storage if the upload to remote storage fails".

Set-up a remote storage backup plan in any subscription.

Run the backup and while the backup is being stored to the remote FTP location, create a failure of the FTP storage location, e.g. block the connection etc. to simulate any kind of remote storage error. Wait until the backup finishes.

ACTUAL RESULT

As defined, the failed backup will be stored in full in the local backup storage. The admin can see it there, e.g. by opening "Account" > "Backup My Account and Websites" list. The admin can also remove it from there:

https://debik.com/plesk_backup_error.jpg

But the subscriber cannot see, neither remove such backups:

https://debik.com/plesk_backup_error_2.jpg

EXPECTED RESULT

The subscriber should own the local backups that result from a storage failure on the remote storage location.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[IgorG]

Peter, here is a reply from the developer:

I was not able to reproduce the issue in any way. It seems the STR are not complete.

 

[Bitpalast]

I have it here on all servers. What is "STR"?

 

[Kaspar]

Steps to reproduce

 

[Bitpalast]

Ah, okay. But it should be very easy to reproduce. For example the same thing happens when the remote storage space is exceeded so that the backup cannot be stored in full. I wonder why it cannot be reproduced at Plesk, because I have seen the same symptom here across all servers for at least a year on many occasions.

 

[IgorG]

Peter, developers have reproduced the issue and found it related to any local backups (never mind whether it was a failed FTP one or just local).
The investigation is ongoing.

 

[IgorG]

Here is the developer's explanation:

The described behaviour is expected and related to both - common local backups and mentioned failed FTP backups. The page Plesk > Account under the customer has two buttons: Back Up My Account and Websites Back Up Websites These are two separate entities and they have separate settings for remote storage. The first one allows creating backups of the customer's settings alongside its websites. Every local backup has its file that looks like this one /var/lib/psa/dumps/clients/jdoe/backup_info_*.xml. The second one shows backups for a specific domain and the data is stored in files like /var/lib/psa/dumps/clients/jdoe/domains/example.com/backup_info_*.xml. As for FTP backups, the backup utilities look into the directory that is explicitly set in Remote Storage Settings > FTP(S). Thus, if the FTP settings are the same under both buttons, the backups for domains will be shown under the first one. However, it will not be possible to restore them: The backup of the type domain cannot be restored now. To restore it, login as the backup owner and click this backup name in Backup Manager. It is predefined behaviour and, in general, it is not recommended to store different backup types (server, reseller, customer, subscription) within the same directory (local or remote).