This article explains how to restore specific database tables from your Web60 backups instead of restoring your entire website.
When to Restore Individual Tables
Restoring specific tables is useful when only part of your database is corrupted or lost. Common scenarios include:
- Lost blog posts or pages (restore wp_posts table)
- Missing user accounts (restore wp_users table)
- Corrupted settings (restore wp_options table)
- Damaged comments (restore wp_comments table)
If multiple tables are affected or you're unsure which ones, consider a full site restore instead.
Understanding WordPress Database Tables
WordPress uses several database tables to store different types of content:
wp_posts - Blog posts, pages, and custom content wp_users - User accounts and login information wp_options - WordPress settings and configuration wp_comments - Comments and comment metadata wp_postmeta - Additional data for posts and pages wp_usermeta - Additional user information
Your table names might have a different prefix instead of "wp_" depending on your installation.
Step 1: Download Your Backup
Log into your Web60 control panel and navigate to the Backups section. Find the backup containing the data you want to restore. Click "Download" and save the backup file to your computer.
If you need help with this step, see downloading your backup files.
Step 2: Extract the Database File
Your backup is a compressed file. Extract it using your computer's built-in tools or a program like 7-Zip. Look for a file ending in ".sql" - this contains your database.
Step 3: Open the Database File
Open the .sql file using a text editor like Notepad (Windows) or TextEdit (Mac). The file contains SQL commands that recreate your database tables.
Step 4: Find the Specific Table
Press Ctrl+F (Windows) or Cmd+F (Mac) to search the file. Search for "CREATE TABLE" followed by your table name. For example, search for "CREATE TABLE wp_posts" to find your posts table.
Copy everything from that CREATE TABLE line down to the end of that table's data. This usually ends with a line containing semicolon (;) before the next CREATE TABLE appears.
Step 5: Access Your Database
In your Web60 control panel, go to the Database section. Click "phpMyAdmin" to open the database management tool.
Step 6: Select Your Database
In phpMyAdmin, click on your website's database name in the left sidebar. This shows all your current tables.
Step 7: Drop the Current Table
Find the table you want to restore in the list. Click the checkbox next to it, then click "Drop" at the bottom. Confirm when prompted. This deletes the corrupted table.
Warning: This permanently deletes the current table. Make sure you have a recent backup before proceeding.
Step 8: Import the Table
Click the "SQL" tab at the top of phpMyAdmin. Paste the table data you copied in Step 4 into the text box. Click "Go" to recreate the table with your backup data.
Step 9: Verify the Restoration
Check your website to confirm the restored data appears correctly. If you restored posts or pages, verify they show up on your site. If you restored users, test that login accounts work.
If you're still stuck with database restoration, contact Web60 support through your control panel. Include details about which table you're trying to restore and any error messages you received.
FAQ
Q: Can I restore tables from different backup dates?
A: Yes, you can restore individual tables from different backups. However, this might cause data inconsistencies if the tables reference each other.
Q: What happens if I restore the wrong table?
A: You can restore it again from a more recent backup, or contact support for help. Always create a manual backup before making changes.
Q: Why can't I see my database in phpMyAdmin?
A: Your database might not be created yet, or you might not have the correct permissions. Contact support if you can't access your database.
Q: How do I know which table contains my missing content?
A: Blog posts and pages are in wp_posts. Users are in wp_users. Settings are in wp_options. Comments are in wp_comments. The table names might have a different prefix.
Q: Can I restore just one blog post instead of the entire wp_posts table?
A: Yes, but this requires finding the specific post data in the SQL file and is more complex. Restoring the full table is usually safer and easier.
Q: What if my backup file is too large to open in a text editor?
A: Large SQL files might need a specialised database tool. Contact Web60 support for help with large database restorations.
Q: Will restoring a table affect my other content?
A: Restoring individual tables only affects the data in that specific table. Other tables remain unchanged, but there might be relationship issues between tables.
Last updated: 1 March 2026