• 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!
  • 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.

Issue Backup does not include all files mentioned

Markus G.

New Pleskian
Plesk Version 12.5.30 Update #70

Following symptoms:

Backup (admin global backup) daily works fine, no errors. (complete backup, no incremental) (was incremental before but to find error we changed to complete backup 3 days ago)

BUT: NOT ALL FILES ARE BACKED UP!!!! (from httpdocs, files from the website and randomly, e.g. some files from one directory are copied, others not)

System says everything is fine, but when we try to restore certain files, we get following error:

Can not deploy content of domain xxxxxxxxxx.com
Warning:
Archiver error: from /var/lib/psa/dumps/resellers/manuel/domains/xxxxxxxxxx.com/backup_user-data_1709120338.tgz: /bin/tar: Unexpected EOF in archive /bin/tar: Error is not recoverable: exiting now

This happens with every backup since 21/08/2017.
We only found it, because the 21/08/2017 backup was 5.3GB large, and 22/08/2016 only 2.56GB
Comparing the backupfiles we found that randomly files are missing
 
This is an interesting error. We recently saw this on a Plesk Onyx restore that should have been correct, too. However, we thought that we might haver overlooked an error message. Maybe there is a bug. If possible, can you open a support ticket with official Plesk support on this?
 
I can only recommend creating a request to support team to do the in-depth investigation to find the reason and to fix it. Please create a ticket to support at Plesk Help Center
 
Back
Top