Restoring WordPress from backup

Tabs prefix was actually easy to change with PhpMyAdmin, so now I have what is supposed to be the old database with old tabs prefixes. Still no sigh of showing any old content.

The database name still doesn’t match with the backup one, should I change it? Oops, if I do I get Error establishing a database connection

What else needs to be put in the right order? I mean the WordPress dashboard works fine but as I said earlier aside from the original plugins nothing else shows up. Yet the solution doesn’t seem to be that far away.

Most table properties are easy to change with phpmyadmin, but if they don’t reflect what Wordpress expects, then it won’t work. This is kind of the same problem with the database name, you can change it easily but it won’t work if Wordpress is set up to use a different one.
You now have the problem that Wordpress wants to use one database and your backup program wants to use a different one, so it’s going to be very difficult to get Wordpress and backup working because they are looking for different databases.
You need to either install Wordpress with the same settings as your backup expects or ignore the backup program and manually import the data from the SQL files because you can only reference one database at a time.
wp-config.php will contain all your Wordpress connection parameters that Wordpress uses to establish the connection.
I really think at this point you have 2 options -
1 Start again but create your new empty Wordpress install with exactly the same settings as the original, the ones used to create the backup - or …
2 Ignore the backup / restore plugin, have a working Wordpress and then try and locate, identify and import the Wordpress content manually

Yeah but make sure you follow up steps:

-Rename the backup file from .wpress to .zip.
-Extract the zip file to a folder on your computer.
-Compress the folder into a zip file again.
-Upload the zip file to your website using WPvivid Backup Pro3.
-Restore the backup using WPvivid Backup Pro3.

You know, I had the same thought.
I would have expected, after I imported the database, to login in and finding the old website environment but as you say WorkPress doesn’t recognize the database. In fact when I log in nothing is there, the site asks to choose a language and to set a new database.

I did follow, out of curiosity, the startup wizard and I set database name, user, etc., being sure to select the backup database name (found inside the SQL) and the database location of the previously imported backup.

Once in, as I anticipated, the dashboard is that of a perfectly new installation. No data from the old site with two exceptions: all old plugins are listed (all outdated and deactivated) and the old theme (also deactivated) is there and can be used. Everything else is not there.

But the thing is it didn’t give me any Error establishing a database connection or similar when I set the database name in the startup wizard or at any time, therefore that means it doesn’t see any particular issues in the database itself but it appears that everything belonging to the old environment are invisible, like orphaned or something like that. So there must be something, as you say, WordPress is expecting to find to accept the old data. But that something we don’t know…

It depends which settings. I have all plugins and themes and I can import what it appears to be the old database (changing tabs prefixes) and also setting the same database name in wp-confing.php. More than that is beyond my knowledge at this particular moment.

I have no idea ATM which areas of the database I should export and what function they have. I guess I will keep it as last resort.

Thanks @lara it seems an interesting thing to try and I’ll give it a try asap thought I’m a bit disenchanted at this stage. Who knows :grinning:

I can find only these two

I chose WPvivid Backup for MainWP but it doesn’t show in the dashboard, how am I supposed to use it?

I am glad my post was useful for you and you are welcome buddy!! I hope you could back all of your data by using WPvivid Backup for MainWP extension. Though it’s a great tool. I see that you have installed the extension on your MainWP dashboard site, but it doesn’t show up in the sidebar menu. That’s strange, it should be there. Maybe you need to enable the WPvivid Backup Plugin on your child sites first.

By enable you perhaps mean activate? I did activate the plugin in plugin section after the download, but no trace of it in the dashboard sidebar.

No, I didn’t mean activation of the plugin, enabling and activating these are two different terms. Follow these steps to enable your WPvivid Backup Plugin: Plugins > Add New in your WordPress dashboard and search for WPvivid Backup Plugin. Then, click on Install Now and then Activate. To activate WPvivid Backup Plugin, you need to go to WPvivid > Settings in your WordPress dashboard and enter your license key in the License tab. Then, click on Activate License and agree to the terms of service.

The unexpected happened! I managed to recover the site using All-in-One WP Migration plugin and I am not joking this time.

All I had to do was increase upload_max_filesize in either php.ini or .htaccess (this one overrides the previous), which I did, but for some reason the old version of All-in-One WP Migration I had installed wasn’t complying with those instructions so I just had to update it.

Thank you so much @kerry14 and @lara for your assistance !!!

2 Likes

Welcome and I am glad you fixed the issue.

1 Like

Hey there,

Man, I’ve been down that rabbit hole, and trust me, it can be a head-scratcher! Like you, I anticipated that importing a backup would bring back the old website environment, but WordPress can be finicky. Just a few thoughts on what you mentioned:

Setting Up A New Database: Sounds like WordPress isn’t associating the old content with the new database. When you set the backup database name and its location from the SQL backup, it’s perplexing that you’re still faced with an entirely new dashboard. However, the fact that the old plugins and theme are there gives a glimmer of hope.

No Database Connection Error: The fact that you’re not getting the infamous ‘Error establishing a database connection’ message suggests, as you rightly pointed out, that the database seems intact. It might be possible that there are certain configurations or paths that need to be set correctly.

Recreating the Original Environment: By settings, I’m hinting at things like table prefix in the wp-config.php file, permalink structures, or even any specific server configurations if you had any. While plugins and themes can be crucial, sometimes these tiny settings can make or break the restoration process.

Manual Import: Definitely a more time-consuming process and, I agree, should be kept as a last resort. Without a clear idea of what tables store what information, it could lead to more confusion.

From what you’ve described, and from my own experiences, it does sound like the data is there in the database but WordPress is just not picking it up. It might be worth checking the database’s user permissions and ensuring they match up, or maybe even cross-referencing the SQL backup to see if the links within are correctly pointing to your current domain and path.

Stay persistent and don’t hesitate to ask around in WordPress communities. There’s always someone who has faced a similar hiccup and figured out a workaround. Fingers crossed you get it all sorted!

Best of luck,
Ahmad

Hi @ishtiaqahmed9834 thanks for your thoughts,

All of the above could be possible and the cause likely was the plugin I used to backup the site. In fact after having done the restoring, the database look like a proper one with at least 100 tabs more that the one I previously imported (and the right prefix).

Who knows, either some portion of database was good enough to be used to generate the new dashboard work environment or most likely it would just generate new tabs and ignore the orphaned altogether in one big mess (although I haven’t noticed any increase of tabs, maybe I would overwrite the ones with the same name?) .

I guess one way would be to ask the plugin author if would be possible to recover the site by just unpacking the backup file, like I did.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.