Hi there,
This could well be due to a plugin conflict, you would need to perform a conflict test.
You could first try disabling only the WP Staging plugin and then running your backup.
Ideally, temporarily disabling all plugins and using a default theme is the best method.
If the issue persists after this please provide the log file using PasteBin or similar means.
Best regards,
Nick
I disabled the WP Staging but same issue. The old database was not deleted.
This is the log:
https://pastebin.com/YV5357wX
pw: ZTfcLLRyEg
Hi there,
Thank you for the log file.
Looking at the log file there are duplicate database tables with different prefixes (examples):
4772.472 (8) Table b6x5H11E6_yoast_primary_term: corresponding file already exists; moving on
4772.473 (8) Table b6x5H11E6_yoast_seo_links: corresponding file already exists; moving on
4772.473 (8) Table b6x5H11E6_yoast_seo_meta: corresponding file already exists; moving on
These tables have been backed up successfully. You then have the other tables (examples):
4772.549 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_primary_term
4772.549 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_seo_links
4772.550 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_seo_meta
So the presence of two sets of database tables is causing the problems you’re experiencing.
UpdraftPlus would not delete database tables, this is not a part of the plugin’s functionality.
You could try replacing the database prefix in the wp-config file: $table_prefix = ‘qny3n_’;
I offer this advice with a note of caution as I can’t be certain the wpstg0 tables are complete.
However, you would still need to delete the old database tables to avoid the same problem.
Best regards,
Nick
So the problem is with UpdraftPlus. Because they were able to backup staging site before June 25.
These are tables from the staging site, therefore they are “duplicate” but without the b6x5H11E6_ prefix. WP Staging with prefix all the table with wpstg0, wpstg1 etc.
Hi there,
The problem is not with UpdraftPlus, it is related to the issues with your installation.
The two sets are the cause of the problem and UpdraftPlus did not create these sets.
It’s likely there weren’t duplicates in those previous staging site backups you mention.
The premium plugin offers the option to exclude any specified tables from the backup.
Best regards,
Nick
I did not say UpDraftPlus created these sets. I said the WP Staging plugin did. For staging, obviously ones needs to duplicate the database. Therefore you will see two sets. The original set is with the prefix b6x5H11E6_ whereas the sets created by WP Staging is prefixed by wpstg0, wpstg1 etc.
UpDraftPlus should be backing up the site, including the staging site’s database. Maybe before June it was dong it. But since June, it throws error and refused to backup staging site data. That is why the problem is with UpDraftPlus and not the WP Staging plugin.
Hi there,
It’s not necessary to have duplicate tables for a staging site with UpdraftPlus.
You can simply create a normal backup and then restore it to the staging site.
If you choose to mix plugins then you may well find you encounter problems.
That doesn’t mean the plugins are the problem, it’s how they are being used.
Based on the info you’ve provided the problem resides with your installation.
You have two sets of database information, which is not standard or normal.
UpdraftPlus is backing up the active database named in wp-config correctly.
I advised previously on how to resolve the issue by removing the duplicates.
Best regards,
Nick
That is not how a normal staging site works. The WP Staging plugin simply duplicate your existing site’s content and create a staging site. One can then change whatever and migrate it to production.
UpDraftPlus has always been backing up the entire database whether it is production or staging. It is apparently that the function has changed. We have no choice but choose other backup solution other than UpDraftPlus.
Hi there,
I think you misunderstood my meaning. By duplicates I mean having two sets of the same database tables with different prefixes in one WordPress installation. One set would be the normal expectation.
There may be more issues. If you can re-share your log file via PasteBin I can look for any other issues.
Best regards,
Nick
-
This reply was modified 1 year, 8 months ago by
nrobertsudp.
Staging is exactly what it is. duplicate database tables with different prefix to identify the staging vs production. But as I have said UpDraftPlus was able to do that before June without any issue. You guys changed it.
If you can’t back up the staging tables now, then it’s an issue already. It won’t matter if there are other issues.
Hi there,
That is not how UpdraftPlus works. Perhaps you need to contact WP Staging support for assistance?
Best regards,
Nick
I tried to backup from a site where I removed the WP Staging. Same issue. The log is below:
https://pastebin.com/DVwruagv
PW: PdwJDfgYmf
