• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.

Issue Hi backup manager crash when i try to restore

dblii

New Pleskian
hi i try to restore a database from my backups and it load for very long, the database i try to restore is just 5MB. FInally the database after 2hours not restored and the progress bar continue loading
 

Attachments

  • Screenshot 2020-04-30 at 3.27.10 PM.png
    Screenshot 2020-04-30 at 3.27.10 PM.png
    111.1 KB · Views: 5
If this is a virtual server with limited cpu power (e.g. 2 virtual cores), it is thinkable that a 45 GB restore takes that long. The reason for it is that the 45 GB needs to be downloaded from the archive location (if that is coming from an external system) and decompressed (on your local machine) first. Then the database can be restored from a dump file inside the archive.

How to find out?

What you can do is to start a shell while the restore is active and enter:
# ps aux | grep pmm

You will find several processes of the backup manager. You can then check whether these processes are actually doing something or whether they are stuck. For example you could

# strace -p <pid>

of a specific one of theses processes to check whether it is doing something.

You could also use the "top" command to see if the backup processes consumes a lot of cpu power (normally a restore does).
 
Back
Top