Backup and Restore function not working as expected?

[seqoi]

Server operating system version

Almalinux 9.5

Plesk version and microupdate number

Plesk Obsidian 18.0.65 Update #2

So I started a new server and I'm studying new tools. I have never used WP Toolkit before, but I said to myself, let's see what Plesk has done. I'm generally a supporter of the "manual" process, but as I said, it's a new server, so I told myself to try some things.

Problem with Backup and Restore. Please tell me what I'm doing wrong. I am installing a new Wordpress instance. Wordpress works flawlessly, the Plesk panel detects the instance properly.

I have the following options in the Wordpress tab: Copy data, Clone, Backup and Restore, check Wordpress integrity and so on.

I go to Backup and Restore. I make a backup. The backup was properly made. Now I go to the Wordpress site itself. For the opportunity to test and describe my query, I will do the following. I am adding four random plugins. Note: 4 plugins were added AFTER the successfully completed backup. I'm playing around with Wordpress settings and I'm not satisfied, let's just say. I say to myself, ok, now let's go to Restore to return to the position before I installed these 4 plugins. In Plesk, I go to the same Backup and Restore. I mark that backup and do Restore. Plesk tells me that everything went successfully.

I log in to Wordpress, but those 4 plugins are still there??? Plesk did not do a full restoration but added files to the existing installation? Although the screenshot suggested that all files created after the backup will be removed, the files were not removed? Screenshot.

Now this already seems to me that there is some kind of option that I have overlooked or is this a serious bug?

 

[Aleksey Filatev]

Thank you for the detailed explanation of the behavior you expected. It is definitely a valid expectation, and it differs from the behavior currently implemented by the product. The WP Toolkit does not remove files that are not present in backups and, similarly, does not remove database tables missed in the backup. For many use cases, this behavior also seems expected.

There are clearly different scenarios, and the behavior should be governed by an option during the restoration. In fact, WP Toolkit has such options, but unfortunately, they are not yet available in UI.

However, these options are presented in the REST API: the option "clobber," which, if true, will remove files missed in the backup, and the option "dropAllDatabaseTables," which, if true, will drop everything in the database before the restoration. Please refer to the REST API (Tools & Settings / Remote API (REST) / WP Toolkit REST API, section /v1/features/backups/restorer) for the details.

As a workaround, you can also consider the ability to use built-in Plesk backup and restore functionality that will behave in accordance with your expectations.

 

[seqoi]

Thank you for the detailed explanation of the behavior you expected. It is definitely a valid expectation, and it differs from the behavior currently implemented by the product. The WP Toolkit does not remove files that are not present in backups and, similarly, does not remove database tables missed in the backup. For many use cases, this behavior also seems expected.

There are clearly different scenarios, and the behavior should be governed by an option during the restoration. In fact, WP Toolkit has such options, but unfortunately, they are not yet available in UI.

However, these options are presented in the REST API: the option "clobber," which, if true, will remove files missed in the backup, and the option "dropAllDatabaseTables," which, if true, will drop everything in the database before the restoration. Please refer to the REST API (Tools & Settings / Remote API (REST) / WP Toolkit REST API, section /v1/features/backups/restorer) for the details.

As a workaround, you can also consider the ability to use built-in Plesk backup and restore functionality that will behave in accordance with your expectations.

Aleksey thank you for your response.

For many use cases, this behavior also seems expected. - that would be a technically incorrect statement. Also unfair a bit.

I will give you the benefit of the doubt because geeks are geeks, they see things differently than the usual world, what can I expect right?

However, follow me closely on this. I say your comment is unfair, especially given the fact your (Plesk) interface tells me this upon restoring backup

"This will remove all site data created after this date" - can it be clearer than this? I am a non-English speaker but this tells me that the data created AFTER this date is going to be removed. And this is exactly what I would expect it to do. And this is exactly what is not happening. So something is wrong. It is either bad wording or your product.

WP Toolkit is not "restoring" from the backup. Instead what it does is "merge" the data which is completely defeating the purpose of "restoration" to an earlier point.

Now in case your (Plesk) wording was different from that window and said something along the lines of ""This will merge all site data created at this date with the data that is currently in your folder and your database" I would know exactly what to expect.

And I don't think it's unusual to expect full restoration.

I just randomly installed 3 backup and restore plugins that were recommended by the WordPress directory. One was Updraft Plus, one was Duplicator and the third one I can not remember the name anymore. Long story short they all behave completely the same in the sense that once you initiate the Restore function it will return your website and the database to a point where it was at the time of a backup exactly 1:1 - they do not use MERGE they use restore.

I suggest you look at how Updraft Backup did their take because with them one can restore just the database, or just the files (leaving the database intact), or just the files minus the database - quite cool.

Now don't point me to "workarounds" because I am well aware of them. Do not offer me something and then when this is not working as expected you are pointing me to something else. That seems a waste of my time.

My English is bad and reading this I see I am coming out harsh but this is not my intention. I can sense WP Toolkit could be nice and as you said, it has the features I expected but they are still hidden or in the beta phase. I sense the product will be good but perhaps in a year or so. No worries I am not depending on it but you should honor someone else's time because when you offer me backup and restore as a feature and then this is not working I feel a bit dumb. I wouldn't if it was marked as a "beta" feature.

WP Toolkit seems to have other problems as well ( Backup and Restore failed ) - out of the blue it stopped restoring backup and then I also realized some other stuff in logs. So Like I said I will continue to use it just for the update digest but overall it still needs to mature.

I wish you all the best inthe new year and Merry Christmas to everyone.