{"id":20406,"date":"2026-11-02T12:26:46","date_gmt":"2026-11-02T11:26:46","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/wordpress-backup-terugzetten\/"},"modified":"2026-11-03T14:54:07","modified_gmt":"2026-11-03T13:54:07","slug":"restoring-a-wordpress-backup","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/wordpress-backup-terugzetten\/","title":{"rendered":"Restoring a WordPress Backup: How to Restore Your Site"},"content":{"rendered":"
\"Restoring<\/figure>\n\n\n\n

After an update, a hack, or a wrong click, your site stops working, and you know there\u2019s a backup somewhere. You can restore a WordPress backup through your hosting control panel or a backup plugin by restoring the files and database from the same restore point. After restoring, check the permalinks and cache, and make sure the cause of the problem wasn\u2019t restored along with the site. If things went wrong after an update, try the simpler solution first Site Down After an Update<\/a>, because often disabling just one plugin is enough. Below, you\u2019ll learn what\u2019s involved in restoring a WordPress backup: the correct restore point, the process, and the follow-up check. This article is part of WordPress Management: The Complete Guide<\/a>.<\/p>\n\n\n\n

Before you begin: three questions<\/h2>\n\n\n\n

Before you restore a backup, you\u2019ll want to know whether you\u2019ve secured the current state of your site, what\u2019s wrong, and whether any new data is still coming in. That\u2019s because restoring means overwriting. It works like rewinding a videotape, where everything recorded after that point is erased. My first piece of advice may therefore seem contradictory. First, back up your broken site\u2014for example, in Installatron. Even a broken site contains today\u2019s orders, form submissions, and text, and this way you can retrieve them later. Many hosting providers do not automatically preserve the current state when restoring, so don\u2019t count on it.<\/p>\n\n\n\n

The second question is whether you know what\u2019s wrong. When there\u2019s been a hack, I never just restore a backup, because the vulnerability is still there and it\u2019ll happen again within a few days. First, fix the root cause, and then verify that the backup is complete\u2014including both files and the database\u2014and that it was created before the infection. You can read about how to do that at Remove malware<\/a>, or you can leave it to WordPress hacked<\/a>. The third question applies mainly to online stores. If any orders or form submissions are still coming in, export them first (see WooCommerce Backup<\/a>) and put the store into maintenance mode<\/a>.<\/p>\n\n\n\n

Which restore point will you choose?<\/h2>\n\n\n\n

The restore point is the date and time of the backup you're restoring, and which point is appropriate depends on what went wrong. Also, you don't always need to restore everything. Often, a partial restore is enough\u2014just the database or just the files\u2014and that way you lose less data.<\/p>\n\n\n\n

Situation<\/th>Select this restore point<\/th>What do you put back?<\/th>Please note<\/th><\/tr><\/thead>
Failed update<\/td>Just before the update<\/td>Often just files<\/td>Don't blindly reinstall the update<\/td><\/tr>
Hack<\/td>Last clean backup\u2014often further back than you think<\/td>Everything<\/td>First, fix the cause, then reinstall the core via Dashboard > Updates<\/strong>, then updates and passwords<\/td><\/tr>
Content deleted or setting incorrect<\/td>Just before the change<\/td>Database only, or the revision via undo changes<\/a><\/td>Everything added to the database after that will be deleted<\/td><\/tr>
Corrupted database<\/td>Last working backup<\/td>Database only<\/td>Files and the database must be compatible<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

That last column is more important than it seems. If you only restore the database while your plugins have since been updated, a plugin may sometimes expect a different database structure than what\u2019s actually there. Files and the database should together form a backup set from the same point in time. If you\u2019re unsure, restore everything. How far back you can go in the event of a hack depends on your hosting plan and how long your backups are retained.<\/p>\n\n\n\n

Restoring a WordPress Backup: Three Methods<\/h2>\n\n\n\n

There are three ways to restore a backup, ranging from simple to technical. I recommend the first one, because it works even if WordPress itself no longer loads. If you're unsure about the restore point, test it first on a clone of your site in Installatron, a simple staging environment<\/a>.<\/p>\n\n\n\n

Through your hosting control panel<\/h3>\n\n\n\n
    \n
  1. Log in to your hosting control panel and open the backup section; for Surver, that's JetBackup 5 in cPanel.<\/li>\n\n
  2. Select the restore point by date and time.<\/li>\n\n
  3. Choose what you want to restore: everything, just the files, or just the database.<\/li>\n\n
  4. Confirm and wait until the repair is complete.<\/li>\n<\/ol>\n\n\n\n

    With a backup plugin<\/h3>\n\n\n\n

    A backup plugin restores data from the WordPress admin panel. In UpdraftPlus, go to Settings > UpdraftPlus Backups<\/strong>, tab Backup\/Restore<\/strong>, check the boxes and click Recover<\/strong>. The downside is that this only works if you can still log in. If the site is down, first install a fresh copy of WordPress and the plugin, and then link the backup from your cloud storage.<\/p>\n\n\n\n

    Manual<\/h3>\n\n\n\n

    You should only perform a manual restore if the other methods are not available. You can import the database into an empty database using phpMyAdmin, or with WP-CLI via wp db import backup.sql<\/code>. Use (S)FTP or the file manager to move the files back to the correct folder, usually especially wp-content<\/code>. Then check in wp-config.php<\/code> or whether the database name, username, and password are correct.<\/p>\n\n\n\n

    After resetting: check the following points<\/h2>\n\n\n\n

    After rolling back, check to make sure the site is working, your data is complete, and the issue has truly been resolved.<\/p>\n\n\n\n

      \n
    1. Clear the cache of your cache plugin and your browser; see clear the cache<\/a>.<\/li>\n\n
    2. If pages return a 404 error, resave the permalinks via Settings > Permalinks<\/strong>.<\/li>\n\n
    3. Log in and check your homepage, a few pages, and the media library. Is the site URL correct, and does Google Search Console report any new errors in the days that follow?<\/li>\n\n
    4. Test your forms and, for an online store, the checkout process, or leave that to WooCommerce Management<\/a>.<\/li>\n\n
    5. Apply the updates that were released after the restore point; otherwise, the old, vulnerable version will be back online. Within WordPress maintenance<\/a> We'll do that for you every month.<\/li>\n\n
    6. After a hack, change all passwords for WordPress, the hosting control panel, and FTP. If you change your database password, you'll also wp-config.php<\/code> at.<\/li>\n\n
    7. Remove orders or submissions made after the recovery point from your export and compare them with your payment provider; see online store offline<\/a>.<\/li>\n<\/ol>\n\n\n\n

      With us, you don't have to worry about making backups yourself. At Managed WordPress Hosting<\/a> We automatically create daily, weekly, and monthly backups on external servers in separate data centers within Europe. You can restore data on the shared hosting plans yourself, free of charge, using JetBackup 5\u2014separately for files, databases, or email accounts. A backup you created in Installatron must be restored in Installatron. JetBackup also does not automatically save your current state, so be sure to create a backup yourself first. If you\u2019re on Surver Cloud, please contact support. And test your backup before you need it. Here\u2019s how to do that and how often you back up your data<\/a>, as you can read in WordPress Backup and Migration: The Complete Guide<\/a> and the maintenance checklist<\/a>.<\/p>\n\n\n\n

      Frequently Asked Questions<\/h2>\n\n\n\n

      How do I restore a WordPress backup if I can no longer log in?<\/strong><\/p>\n\n\n\n

      In that case, use your hosting control panel or the manual method with phpMyAdmin and (S)FTP. A backup plugin only works if WordPress itself is still loading. If neither of these options works, install a fresh copy of WordPress and reconnect the backup plugin.<\/p>\n\n\n\n

      How long does it take to restore a backup?<\/strong><\/p>\n\n\n\n

      That depends on the size of your site and your media library. Using the hosting control panel usually takes just a few minutes, but doing it manually takes longer. You should also allow time for a follow-up review.<\/p>\n\n\n\n

      Can Surver restore the backup for me?<\/strong><\/p>\n\n\n\n

      For shared hosting plans, you can restore it yourself, free of charge, using JetBackup 5 in cPanel. If you're unsure which restore point to choose, Surver's support team will help you figure it out.<\/p>","protected":false},"excerpt":{"rendered":"

      Na een update, een hack of een verkeerde klik werkt je site niet meer, en je weet dat er ergens een back-up staat. Een WordPress back-up zet je terug via je hostingpaneel of back-upplugin door de bestanden en de database uit hetzelfde herstelpunt terug te zetten. Controleer na herstel de permalinks, cache en of de […]<\/p>\n","protected":false},"author":2,"featured_media":20528,"template":"","kennisbank_categorieen":[62],"class_list":["post-20406","kennisbank","type-kennisbank","status-publish","has-post-thumbnail","hentry","kennisbank_categorieen-wordpress"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank\/20406","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank"}],"about":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/types\/kennisbank"}],"author":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media\/20528"}],"wp:attachment":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media?parent=20406"}],"wp:term":[{"taxonomy":"kennisbank_categorieen","embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank_categorieen?post=20406"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}