• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

hansitheking

Basic Pleskian
I am running my server with Ubuntu 18.04. Since the Update to Plesk Obsidian 18.0.26 the incremental backup to my FTPS server fails with a message like this:

Code:
Error:
Export error: Size of volume backup_2004190206.tar 2144821247 does not match expected one 2146435072. The remote backup may not be restored.
Error:
Unable to validate the remote backup. It may not be restored. Error: Unable to extract dump header

Files are stored successfully on the remote backup server. I am using the following settings:
- Create a multivolume backup, volume size (MB) of 2047 MB
- Stored in FTP(S) only.
- Exluding Log
 
I luckily did not have the needed yet.
I also do separate db export if i do major changes as its faster to restore
 
The backups with such errors may be not valid and not usable because of issues with network/remote storage.
 
In general I recommend to use another FTP storage or one of cloud storages (Amazon S3, Google Drive, OneDrive, Dropbox) to avoid such errors.
 
Sorry I am using this FTP Storage for 5 years without problems and now since 18.0.26 I have this Problems. Also incremental Backups are not working due to this issue. All the mentioned Cloud storages do not comply with our GDPRs for the mails within the backups. For security I have setup I rync backup for the moment.
 
The feedback for my provider is that if I have access to my FTP backup Server then this disturbing message is plesk related.
All was fine till a good week ago.
Any expert might be able to help to resolve this ??

Error:
Unable to validate the remote backup. It may not be restored. Error: Unable to extract dump header
 
Try to use passive mode on page Backup Manager > Remote Storage Settings > FTP(S) Storage Settings.
 
ok. additional to "Use FTPS" , I now ticked "used Passive mode"

The ftp server can only be accessed from Providers own network.
 
Hi thechanged Passive Mode has NOT changed anything.

The error now reads

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
 
Try to use passive mode on page Backup Manager > Remote Storage Settings > FTP(S) Storage Settings.
I was using passive mode already and I tried also to enable store the backup locally as well and I reduced multivolume volume size to 1024 MB. Still, the same problem. Next I will try to change the protocol to SFTP.
 
I have the same problem for about a month, with no problems before. Backups are huge, the problem is by design, I have to backup 400+GB to FTP every day, that is inefficient if some subscriptions did not change at all in size, why should Plesk have a need to backup everything?
 
I have the same problem for about a month, with no problems before. Backups are huge, the problem is by design, I have to backup 400+GB to FTP every day, that is inefficient if some subscriptions did not change at all in size, why should Plesk have a need to backup everything?
There was issue PPPM-11825 in Plesk Obsidian < 18.0.26.

If workarounds above do not help I recommend to enable verbose logging in /usr/local/psa/admin/conf/panel.ini
[debug]
enabled = 1

[log]
priority = 7

and in /usr/local/psa/admin/share/pmmcli/pmmcli-rc
FORCE_DEBUG_LOG 1

and try to find errors in /var/log/plesk/PMM/backup-<date_time>/backup.log especially in lines with text "Curl output:".
 
Back
Top