Backup and Restore failed

[seqoi]

Server operating system version

AlmaLinux 9.5

Plesk version and microupdate number

18.0.65 #2

So I just tried to restore a backup created today. This is the error and what I am being presented with:

Failed to restore site from backup

• Unable to import database. Error message: mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
• WARNING: option --ssl-verify-server-cert is disabled, because of an insecure passwordless login.

Here is what it is very concerning (for me):

- I am already running MariaDB 11.4.4.
- Plesk didn't update, no changes have been made
- All of my SSL certificates work as expected
- On the VERY same server, just 7 hours ago (before I went to sleep) I could go through the backup and restore process itself without any error on the very same domain/subscription. This just started happening after I tried to run Restore to test the WP Toolkit. So kinda like out of the blue.

The worst of all is that that Restore button in the Plesk doesn't work anymore. As if it does nothing after that. I go and pick that archive, click Restore again to see what will happen and it really does nothing. Clicking Restore present me with the usual little pop up saying that all files after that date will be removed, I click at the red button "Restore" and it closes and nothing happens.

Terrible experience.

 

[seqoi]

Update: I went to select another backup for restoration, created a few days ago and this time error is different:

Failed to restore site from backup

• Error: Error establishing a database connection.
  

Restarted a server, like desperate action.. the same result. a very inconsistent experience. Yesterday it worked, today not.

 

[seqoi]

And of course, my website is ruined after the unsuccessful restoration. Luckily it was a playground experiment. I am not going to use this WP Toolkit Backup and restore anymore until this is fixed.

 

[seqoi]

Went thru the WordPress repair only to end up in a loop asking me to redo it again.

So the point of the story and my experience with WP Toolkit is this. WP Toolkit - avoid backing up and restoring unless you want to screw yourself. Rely on manual-custom processes as usual. The only thing WP Toolkit is good at is reporting updates on plugins and disabling WP cron - in my experience.

A screenshot of my log is attached. As you can see what seemingly worked perfectly yesterday, just 7 hours later doesn't work while no updates to the OS or to the Plesk have been made.