• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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