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