Web Site empty after restore

Resolved Cedric
(@labrauge24)

2 years ago

Hello,

I tried to restore my website (everything: db, themes, plugins, others, uploads).

At the end of the operation, Updraft said that restore was performed successfully.

However, when I log to wordpress, I am not able to retrieve any of my pages.

Could you please help me?

The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)

Plugin Contributor bcrodua
(@bcrodua)

2 years ago

Hi,

To help us work out the cause of your problem, can you please send us a copy of the restoration log?
You can find this log in the ‘wp-content/updraft’ directory of your site via FTP.
You can send the log file as an attachment or copy the contents into an online tool (such as http://pastebin.com/ )

Best Wishes,
Bryle

Thread Starter Cedric
(@labrauge24)

2 years ago

Hi,

It seems that the restore action from UpdraftPlus has not restored correctly the database.

When launching wordpress, in “pages” menu, nothing was displayed : all my pages have gone.

I have been able to solve my issue, by restoring the database directly from my website host .

However, I would be interested to know, what was the issue with Updraft.

Here are the logs:

https://pastebin.com/39A5Y4YE

Thanks in advance

Plugin Support vupdraft
(@vupdraft)

2 years ago

Hi,

Unfortunately this is abackup log rather than a restoration log, can you send us the restoration log from the wp-content/updraft directory of the restored site?
Thread Starter Cedric
(@labrauge24)

2 years ago
Hello,

Sorry, I paste the wrong file. Here are the restore logs:

https://we.tl/t-J9jPqU1b1z

Note: pastebin does not allow me to publish the log in public

Regards, Cedric
- This reply was modified 2 years ago by Cedric.
Plugin Support vupdraft
(@vupdraft)

2 years ago

The restoration log says that the restore successfully completed.

However, there are a number of non core tables that were omitted from the backup and so were not restored.

You will need this add on to backup the tables: https://updraftplus.com/shop/moredatabase/

Thread Starter Cedric
(@labrauge24)

2 years ago

Hello,

The following tables are belonging to the previous website, that is not used anymore, so no issue if they are not backuped:

0106.950 (0) Skipping table (lacks our prefix (wor7834_)): Calendrier
0106.951 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_ban
0106.953 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_censure
0106.954 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_config
0106.955 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_img_verif_add
0106.957 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_messages
0106.958 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_sessions
0106.959 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_smileys
0106.961 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_txt_lang
0106.962 (0) Skipping table (lacks our prefix (wor7834_)): alex_livre_users
0106.964 (0) Skipping table (lacks our prefix (wor7834_)): calendrier
0106.968 (0) Skipping table (lacks our prefix (wor7834_)): tursac24

However, my current website in production, is a full wordpress website, so I don’t understand why I would need the mentioned add on.

I do not know what are the following tables that were not backuped:

0106.970 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_commentmeta
0106.971 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_comments
0106.972 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_links
0106.974 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_options
0106.975 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_postmeta
0106.977 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_posts
0106.978 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_term_relationships
0106.980 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_term_taxonomy
0106.981 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_termmeta
0106.983 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_terms
0106.984 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_usermeta
0106.985 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_users

Plugin Support vupdraft
(@vupdraft)

2 years ago

I think what is happening it is treating these tables which would normally be core tables

0106.970 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_commentmeta
0106.971 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_comments
0106.972 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_links
0106.974 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_options
0106.975 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_postmeta
0106.977 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_posts
0106.978 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_term_relationships
0106.980 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_term_taxonomy
0106.981 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_termmeta
0106.983 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_terms
0106.984 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_usermeta
0106.985 (0) Skipping table (lacks our prefix (wor7834_)): wor5679_users

As non core as it thinks the corresponding tables (with the wor7834) prefix are the core tables.

You will need to remove the old DB. You should then find that it backs up the above tables:

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Web Site empty after restore’ is closed to new replies.