• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Unable to clear restore job from Backup Manager

paul.jazz

New Pleskian
Using Plesk Panel 10.2.0

Within the Plesk Backup Manager I can see an informational message along these lines...

Restoring: backup_domain.co.uk_info_1107120349.xml Refresh

When attempting a restore using /usr/local/psa/bin/pleskrestore my Putty session disconnected. Since then I have been unable to remove this job. No server resources are being used, can't find any running Unix process for this. The server has been rebooted several times, but still cannot clear the message.

The domain backup was less than 100MB so of course over 24 hours later there is no way this should still be running.

Anyone have any ideas how to 'cleanup' the restore process and remove this message?

I have deleted the domain in Plesk and readded, but the error is still present.

Many thanks
 
Information about all current tasks stored at /usr/local/psa/PMM/tasks. If you sure that at this moment no active backup or restore tasks on your server you may just remove all files from this directory. More safer way
1. call /usr/local/psa/admin/bin/pmmcli --get-tasks-list Restore | grep '<task task-id'
2. Remove only files which names specified in 'task-id ' attribute.

Could you provide '/usr/local/psa/admin/bin/pmmcli --get-tasks-list Restore' output before files removing? It allows us to fix this issue in future releases.
 
Back
Top