Backup not success

Tagged: Database

This topic has 4 replies, 2 voices, and was last updated 8 years, 6 months ago by Jatupon.

Viewing 5 posts - 1 through 5 (of 5 total)

Author

Posts
April 28, 2016 at 2:28 am #153860
Jatupon
Participant
It seem none of pages/posts had import when I migrate. I upload the backup files to the server and run the restoration there.

Also it is happen with other plugin that use the same style backup too. I mean the plugins that Have to install WordPress first and run import.

Report as below
```
Final checks

Looking for db archive: file name: backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-db.gz
Archive is expected to be size: 870.4 KB: OK
Looking for plugins archive: file name: backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-plugins.zip
Archive is expected to be size: 13210.9 KB: OK
Looking for themes archive: file name: backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-themes.zip
Archive is expected to be size: 6808.8 KB: OK
Looking for uploads archive: file name: backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-uploads.zip
Archive is expected to be size: 364744.6 KB: OK
Looking for others archive: file name: backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-others.zip
Archive is expected to be size: 472.5 KB: OK
Database

Unpacking backup...
Restoring the database (on a large site this can take a long time - if it times out (which can happen if your web hosting company has configured your hosting to limit resources) then you should use a different method, such as phpMyAdmin)...
Enabling Maintenance mode…
Backup of: https://www.wpthaiuser.dev
Content URL: https://www.wpthaiuser.dev/wp-content
Uploads URL: https://www.wpthaiuser.dev/wp-content/uploads
Old table prefix: wp_
Site information: multisite = 0
New table prefix: wp_74f6036197_
Restoring table (InnoDB): wp_options - will restore as: wp_74f6036197_options
Table prefix has changed: changing option table field(s) accordingly: OK
Elegant themes theme builder plugin data detected: resetting temporary folder
Search and replacing table: wp_74f6036197_options: rows: 347
Restoring table (InnoDB): wp_users - will restore as: wp_74f6036197_users
Search and replacing table: wp_74f6036197_users: rows: 1
Restoring table (InnoDB): wp_usermeta - will restore as: wp_74f6036197_usermeta
Table prefix has changed: changing usermeta table field(s) accordingly: OK
Search and replacing table: wp_74f6036197_usermeta: rows: 38
Restoring table (InnoDB): wp_commentmeta - will restore as: wp_74f6036197_commentmeta
Search and replacing table: wp_74f6036197_commentmeta: rows: 0
Restoring table (InnoDB): wp_comments - will restore as: wp_74f6036197_comments
Search and replacing table: wp_74f6036197_comments: rows: 5
Restoring table (InnoDB): wp_links - will restore as: wp_74f6036197_links
Search and replacing table: wp_74f6036197_links: rows: 0
Restoring table (InnoDB): wp_postmeta - will restore as: wp_74f6036197_postmeta
Search and replacing table: wp_74f6036197_postmeta: rows: 235
Restoring table (InnoDB): wp_posts - will restore as: wp_74f6036197_posts
An error (1) occurred: - The used table type doesn't support FULLTEXT indexes - the database query being run was: CREATE TABLE <code>wp_74f6036197_posts</code> ( <code>ID</code> bigint(20) unsigned NOT NULL AUTO_INCREMENT, 
```
post_autho …
An error (2) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (2, 1, ‘2016-04-26 20:14:24’, ‘2016-04-26 20:14:24’, ‘This …
An error (3) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (1383, 1, ‘2014-09-20 21:36:36’, ‘2014-09-20 14:36:36’, ‘<h …
An error (4) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (4212, 1, ‘2015-07-13 07:48:51’, ‘2015-07-13 00:48:51’, ”, …
An error (5) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (6550, 1, ‘2015-10-11 01:58:32’, ‘2015-10-11 01:58:32’, ”, …
An error (6) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (7255, 1, ‘2015-10-11 02:00:40’, ‘2015-10-11 02:00:40’, ”, …
An error (7) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (10372, 1, ‘2016-03-23 20:55:07’, ‘2016-03-23 13:55:07’, ‘[ …
An error (8) occurred: – Table ‘wprolling-wp-BaOj8pnn.wp_74f6036197_posts’ doesn’t exist – the database query being run was: INSERT INTO wp_74f6036197_posts VALUES (11647, 1, ‘2016-04-27 10:37:05’, ‘2016-04-27 10:37:05’, ‘[ …
Database queries processed: 50 in 2.44 seconds
Search and replacing table: wp_74f6036197_posts: rows: 0
Restoring table (InnoDB): wp_term_relationships – will restore as: wp_74f6036197_term_relationships
Skipping this table: data in this table (wp_74f6036197_term_relationships) should not be search/replaced
Restoring table (InnoDB): wp_term_taxonomy – will restore as: wp_74f6036197_term_taxonomy
Search and replacing table: wp_74f6036197_term_taxonomy: rows: 35
Restoring table (InnoDB): wp_termmeta – will restore as: wp_74f6036197_termmeta
Search and replacing table: wp_74f6036197_termmeta: rows: 0
Restoring table (InnoDB): wp_terms – will restore as: wp_74f6036197_terms
Search and replacing table: wp_74f6036197_terms: rows: 35
Restoring table (InnoDB): wp_et_bloom_stats – will restore as: wp_74f6036197_et_bloom_stats
Search and replacing table: wp_74f6036197_et_bloom_stats: rows: 0
Restoring table (InnoDB): wp_et_social_stats – will restore as: wp_74f6036197_et_social_stats
Search and replacing table: wp_74f6036197_et_social_stats: rows: 0
Restoring table (InnoDB): wp_podsrel – will restore as: wp_74f6036197_podsrel
Disabling Maintenance mode…
Search and replacing table: wp_74f6036197_podsrel: rows: 0
Finished: lines processed: 69 in 2.52 seconds
Cleaning up rubbish…
Database: search and replace site URL

Database search and replace: replace https://www.wpthaiuser.dev in backup dump with https://wprolling.com

Search and replacing table: wp_74f6036197_commentmeta: already done
Search and replacing table: wp_74f6036197_comments: already done
Search and replacing table: wp_74f6036197_et_bloom_stats: already done
Search and replacing table: wp_74f6036197_et_social_stats: already done
Search and replacing table: wp_74f6036197_links: already done
Search and replacing table: wp_74f6036197_options: already done
Search and replacing table: wp_74f6036197_podsrel: already done
Search and replacing table: wp_74f6036197_postmeta: already done
Search and replacing table: wp_74f6036197_term_relationships: already done
Search and replacing table: wp_74f6036197_term_taxonomy: already done
Search and replacing table: wp_74f6036197_termmeta: already done
Search and replacing table: wp_74f6036197_terms: already done
Search and replacing table: wp_74f6036197_usermeta: already done
Search and replacing table: wp_74f6036197_users: already done

Tables examined: 14
Rows examined: 696
Changes made: 127
SQL update commands run: 126
Errors: 0
Time taken (seconds): 0.278

Plugins

Unpacking backup… (backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-plugins.zip, 12.9 Mb)
Moving old data out of the way…
Moving unpacked backup into place…
Cleaning up rubbish…
Themes

Unpacking backup… (backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-themes.zip, 6.6 Mb)
Moving old data out of the way…
Moving unpacked backup into place…
Cleaning up rubbish…
Uploads

Unpacking backup… (backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-uploads.zip, 356.2 Mb)
Moving old data out of the way…
Moving unpacked backup into place…
Cleaning up rubbish…
Others

Unpacking backup… (backup_2016-04-28-0142_WPThaiuser_3afba1ae2557-others.zip, 0.5 Mb)
Cleaning up rubbish…
Restore successful!

Actions: Return to UpdraftPlus Configuration
`
April 28, 2016 at 9:31 pm #154063

udadmin
Keymaster

Hi,

It looks like the MySQL server on your destination site has critical features turned off – either that, or the source site used some unusual MySQL feature. Please can you link the restoration log file? (This has more information than the text on the restore screen that you’ve copy-and-pasted). You can get this from wp-content/updraft on the destination site.

David

April 29, 2016 at 1:31 am #154084

Jatupon
Participant

Hi.

I move from the localhost that use DesktopServer 3.8.1 to DigitalOcean. The php version is different also as I use php 7.0.5 on DO. Actually I already success move from digitalocean to digitalocean use Migrate tool. It is same site. I make the localhost one because I want to build from new setup as the old one have a lot useless pictures. Even though I already sucess with the migration which move from DO > DO (same php version and both use serverpilot to setup wordpress) but we do need to know how the problem could happen and for the future fix. I create new dropet and try again with the same way I used to do.

The log is here. https://www.dropbox.com/s/5dudexvzz2hhk2g/log.9b8f786be000.txt?dl=0

Thank you.

April 30, 2016 at 12:45 pm #154275

udadmin
Keymaster

Hi,

Thank you. The error message and log indicate that on your destination webserver, the InnoDB engine does not support full text indexes, but that your source WordPress database uses these.

From Googling, it looks like the plugin “Contextual Related Posts” has adjusted the “posts” table in the WP database, to use this feature on the source site. It might be best to ask them for guidance on the exact requirements, when migrating to a new site, to make sure that the destination MySQL server is compatible.

David

April 30, 2016 at 1:02 pm #154278

Jatupon
Participant

Exellent! I have uninstall that plugin and try to migrate again only the database and It work like a charm. So I think only this plugin is a problem.

Thank you very much for your support! I am appreaited.
Emily
Author

Posts

Viewing 5 posts - 1 through 5 (of 5 total)

The topic ‘Backup not success’ is closed to new replies.