Backup exclusions can keep disposable caches or reproducible build files out of an archive. They also remove those files from that recovery point, so use a narrow, documented rule rather than excluding a large directory simply to make a backup smaller.
IN THIS ARTICLE
What you need before you begin
Identify which files can actually be regenerated. Keep application configuration, uploads and required custom code unless another verified backup protects them. Database content has its own backup selection and is not excluded by a website-file pattern.
01 Exclude selected files from a Plesk backup
- Open the subscription Backup & Restore page and start a manual backup or edit the relevant scheduled backup settings.
- Find the file-exclusion option in the backup form. Enable it only for the job that needs the rule.
- Enter paths in the format requested by Plesk, relative to the subscription location. A rule such as
/httpdocs/cache/*is appropriate only if that is the actual cache directory for this subscription. - Prefer a specific directory or filename. Check wildcard matching carefully: a broad rule such as
*.zipmay also exclude business documents or application assets that happen to use that extension. - Save the schedule or run the backup. Record why each exclusion exists and what recreates the excluded data. Review the rule again when the website structure changes.
How do I check which files were excluded from the backup?
Inspect the completed backup through available restore selections or a test restore. Confirm that intended files were excluded and that essential neighbouring files remain recoverable. Verify that the application can regenerate the excluded cache.
Troubleshoot unexpected results
If the archive is unexpectedly small, stop replacing older recovery points until you review the patterns. Remove the suspect exclusion and create a fresh backup. An exclusion cannot retroactively add a missing file to an existing archive; restore it from another copy or regenerate it safely.