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

Issue I was hoping this bug would be fixed by now (after years)

Do you want the original dates of your files after you restore a back-up?

  • No, I don't care about the dates of the files as long as they are restored.

    Votes: 0 0.0%
  • No, I prefer to have the time of the restore so I can see when all my files were restored.

    Votes: 0 0.0%

  • Total voters
    4
  • Poll closed .

mr-wolf

Silver Pleskian
Plesk Guru
I'm not doing this quite often so I am not confronted with this each time, but ever since the back-up extension has been upgraded to a more versatile one it does not restore the files with its proper dates.

All files of the site get a timestamp of the moment the back-up is restored.
The timestamps of these files is valuable information.

This is not acceptible!!!
I have reported this several years ago and nothing is being done about it.
A back-up is a back-up and a restore should bring me back my files with its proper dates.
This is data-loss!!!!

Now each time I need to do a restore I need to go to /var/libs/psa/dumps to extract the userdata.tgz of the domain and do a copy of the files to the /var/www/vhosts/<domain>/httpdocs folder.

The good thing about this bug is that it's in the restore module and not in the back-up module.

Fix this by now!!!
I have been waiting for it for years.
 
Back
Top