• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Backup targets of symlinks via Backup Manager

King555

Regular Pleskian
Server operating system version
Ubuntu 18.04.6 LTS x64
Plesk version and microupdate number
Plesk Obsidian 18.0.45 update #2 web admin edition
I have one subscription where the folder inside vhosts/... contains one symlink, which points to another directory on the harddisk. I backup this folder weekly automatically via the Plesk Backup Manager. Unfortunately the symlink target is not backed up. The backup file only contains one 0-byte file with the name of the symlink.

I know how I can fix this with manual backups when using "tar", but can I fix it with the automatic backups?
 
Meanwhile I think it must be a permission thing and the user, which does the backup, cannot access the target of the symlink.

How can I find out which user runs the backup?
 
It seems like this is not possible with Plesk, so I will backup this directory via my own script and a cronjob. Probably it's also safer, because the directory is not revealed to the public when it's not symlinked in the vhost folder (although it's always blocked via a .htaccess file).

So this topic is kind of resolved.
 
Back
Top