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

Issue Scheduled full Backup via Plesk Panel is not a full backup

mw004

New Pleskian
Why scheduled full backup via Plesk Panel does not include all files and directories in httpddocs?
 
Check Backup Settings of your Scheduled backup, especially the "Exclude specific files from the backup" option.
 
Nothing is excluded except emails! But the backup is not complete.
 

Attachments

  • backup.jpg
    backup.jpg
    58.5 KB · Views: 6
What exactly was not included in the backup? More details?
 
Some files and directories from httpsdocs. And the full backup should archive everything. But they are gone ...
There are a number of conditions under which a backup may not complete or may cause minor backup issues:
  1. If disk space at the time of the backup is run is insufficient
  2. A non-storage resource issue at the time of backup
  3. File thrashing (i.e. files that change in the instant that the backup job and the actual zip process takes place)
  4. If you have custom or unique permissions on files or directories that don't enable access to the backup job
  5. If the files or directories are symbolic links
When you say "they are gone" do you mean that you removed the directories and your backups don't show them? It looks like you have a five day retention policy so if the directory in question was removed six days ago, it would not be expected behavior to see the removed directory in the backups for the last five days.
 
Maybe the user means a different directory outside the /var/www/vhosts structure, because he is writing about "htttpddocs"?

Excellent point - in which case that's not a built-in feature of Plesk backups (backing up arbitrary directories outside of the vhosts directory).
 
Everything is fine. There was a bug in unpacking the files. With another archiver, everything is fine.

By the way - in case of a backup error, where can I see what the problem is?

There is no error in this log

/var/log/plesk/PMM/backup-2021-05-04-01-22-02-624/backup.log
 
Back
Top