How to Restore Your Website From a Backup

Overview

A website backup gives you a way to recover from problems by returning your website or hosting data to an earlier state.

You may need to restore a backup after:

A failed website update
Accidental file deletion
A broken plugin or theme
Database problems
A failed migration
A configuration mistake
A security incident
Other unexpected website problems

Restoring a backup can replace existing information, so it should be done carefully.

Before restoring anything, make sure you understand what the backup contains and what information it will replace.

Before You Restore Anything

First, determine what is actually broken.

Ask yourself:

Is the entire website down?
Are only certain pages affected?
Did the problem begin after an update?
Are only the website files affected?
Is the database affected?
Is email affected?
Is the problem actually related to DNS or SSL?

Not every problem requires a complete restoration.

If you can safely fix the specific problem without restoring an older version of the website, that may be preferable.

Create a Backup of the Current State

If possible, create or preserve a backup of the website's current state before restoring an older backup.

Even if the current website is broken, it may contain information that you need later.

For example, it could contain:

Recent customer orders
New blog posts
Form submissions
Uploaded files
New user accounts
Other recent database changes

Having a copy of the current state gives you something to return to if the restoration doesn't produce the expected result.

Choose the Correct Backup

Select a backup that was created before the problem occurred.

For example:

Monday — Website working
Tuesday — Backup
Wednesday — Major update
Thursday — Website breaks
Friday — Current state

A Tuesday backup may be a useful restoration point.

However, don't automatically choose the newest backup available.

If the website was already compromised or damaged when a backup was created, restoring that backup may simply restore the same problem.

Understand What You Are Restoring

A backup may contain:

Website files
Databases
Email
Configuration
Other hosting account data

You may not need to restore everything.

For example:

A deleted image may only require restoring a file.
A damaged WordPress database may require a database restoration.
A failed WordPress update may require restoring website files and possibly the database.
A complete website failure may require restoring both files and database.

Always review the restoration options before confirming the operation.

Use Your Hosting Backup System When Available

Have Freedom Hosting may provide backup and restoration tools depending on your hosting plan and account configuration.

If a restoration interface is available through your hosting account or cPanel, use the provided restoration options whenever practical.

The exact interface and available options can vary between hosting plans and server configurations.

Before confirming a restoration, carefully review:

Which website or account is being restored.
Which backup point is being used.
Which files or data will be replaced.
Whether newer information will be overwritten.

Restoring Website Files

If the problem involves website files, you may be able to restore those files from a backup.

A primary website is commonly located under:

public_html/

Additional domains and subdomains may have different document roots.

You can review your domains and their document roots through:

cPanel → Domains

If you need to manually restore website files, cPanel's File Manager is available through:

cPanel → Files → File Manager

For larger or more complicated restorations, use the backup system provided by your hosting account when available.

Restoring a WordPress Database

WordPress stores much of its website content in a database.

A database restoration may be necessary if the database has been damaged or needs to be returned to an earlier state.

Database management is available through:

cPanel → Databases → phpMyAdmin

Manual database restoration can overwrite current database information.

If you're unsure which database belongs to your WordPress installation or which backup should be restored, don't guess.

Contact Have Freedom Hosting Support before proceeding.

Restoring a WordPress Website

A complete WordPress restoration may require both:

WordPress Files
+
WordPress Database

Restoring only one may leave the website in an inconsistent state.

For example, restoring old WordPress files while keeping a significantly newer database may result in compatibility or content problems.

When possible, restore the matching files and database from the same backup point.

Restoring Email

Website restoration and email restoration are separate considerations.

If your hosting account provides email, determine whether the backup you're restoring contains:

Mailboxes
Email messages
Email settings
Other email-related data

Do not assume that restoring your website automatically restores your email.

If email is important to your business, take care when selecting restoration options so you don't unintentionally replace newer mail data.

Restoring DNS

DNS is also separate from your website files.

If your DNS is managed through cPanel, review it through:

cPanel → Domains → Zone Editor

If your DNS is managed by your domain registrar or another DNS provider, restoring website files will not necessarily restore those DNS records.

If the website still isn't reachable after a restoration, verify that DNS is pointing to the correct hosting service.

Restoring After a Failed WordPress Update

If a WordPress, plugin, or theme update caused the problem, a complete restoration may not always be necessary.

Before restoring everything, consider whether the problem can be isolated to:

A plugin
A theme
WordPress core
PHP compatibility
A configuration change

If you can safely reverse the specific change, you may be able to recover the website without losing newer content.

If the problem is more extensive, restoring a known-good backup may be appropriate.

Restoring After a Security Problem

If you're restoring a website because you believe it was hacked, don't treat the restoration as the entire solution.

You should also consider:

Updating WordPress.
Updating plugins and themes.
Removing unused software.
Reviewing administrator accounts.
Changing compromised passwords.
Reviewing FTP accounts.
Checking for suspicious files.
Checking for unexpected DNS changes.
Identifying how the compromise occurred.

Otherwise, the same vulnerability may allow the website to be compromised again.

If you suspect your hosting account itself has been compromised, contact Have Freedom Hosting Support.

After the Restoration

Once the restoration finishes, thoroughly test the website.

Check:

Homepage
Important pages
WordPress administration
Navigation
Images and media
Contact forms
User accounts
Database-driven features
Online store functionality
Checkout
Email
HTTPS
Any important third-party integrations

Don't assume that a successful restoration message means the website is completely functional.

Clear Website Caches

If your website uses caching, clear the applicable caches after restoring it.

This may include:

WordPress caching plugins
Hosting/server caching
CDN caching
Browser caching

Otherwise, you may continue seeing an older version of the website.

Check SSL and HTTPS

After restoring a website, verify that HTTPS still works correctly.

Test:

https://yourdomain.com

If you see certificate warnings, mixed-content errors, or redirect problems, the issue may be unrelated to the restored files.

Check your domain, SSL configuration, and DNS if necessary.

Check WordPress Updates

A backup may restore older versions of WordPress, plugins, or themes.

Once the website is stable again, review:

WordPress Dashboard → Updates

Don't immediately update everything at once.

First determine what caused the original problem, create another backup, and then perform necessary updates carefully.

Check Your PHP Version

A restored website may depend on a particular PHP version.

You can review your domain's PHP configuration through:

cPanel → Software → MultiPHP Manager

If the restored website behaves differently from the previous version, PHP compatibility may be worth checking.

Don't repeatedly change PHP versions without knowing what the website requires.

If the Restoration Didn't Fix the Problem

If the website remains broken after restoring a known-good backup, the problem may not have been contained in the restored data.

Possible causes include:

DNS problems
SSL problems
PHP compatibility
Server configuration
External services
Third-party APIs
Caching
A security vulnerability
Incorrect permissions
Problems outside the website itself

At this point, gather the relevant error messages and contact Have Freedom Hosting Support.

Common Restoration Problems

"My Recent Content Disappeared"

You may have restored an older backup.

Anything created after that backup may no longer be present in the restored version.

If the missing information is important, preserve the current state and investigate whether it can be recovered separately.

"The Website Works, but Some Things Are Missing"

The backup may not have contained everything required.

For example, it may have included website files but not the database, or vice versa.

Check what was included in the backup.

"The Website Is Still Broken"

The backup may have been created after the problem began, or the problem may be unrelated to the website data.

Check DNS, SSL, PHP, caching, and other hosting components.

"My Website Looks Fine, but Email Is Missing"

Website restoration does not necessarily restore email.

Check whether the restoration included mailbox data before assuming the email was lost.

"The Restoration Tool Isn't Working"

Do not repeatedly attempt the restoration without understanding the error.

Record the error message and contact Have Freedom Hosting Support.

What Not to Do

Avoid:

Restoring random backups.
Overwriting a working website without a recovery plan.
Restoring an old database without knowing which website it belongs to.
Deleting current data before preserving it.
Assuming a security problem is fixed simply because a backup was restored.
Changing DNS, PHP, SSL, and WordPress configuration simultaneously while troubleshooting.

Make one meaningful change at a time whenever possible.

A Simple Restoration Process

When you need to restore a website:

Identify what is broken.
Determine when the problem started.
Preserve the current state when possible.
Identify available backups.
Choose a backup from before the problem.
Determine whether files, databases, email, or other data need restoration.
Review what the restoration will replace.
Perform the restoration.
Test the website thoroughly.
Clear applicable caches.
Check HTTPS, DNS, PHP, and WordPress compatibility.
Address the original cause of the problem.
Create a fresh backup once everything is working correctly.

Need Help?

If you're unsure which backup to restore or what information will be replaced, contact Have Freedom Hosting Support before proceeding.

When contacting support, provide:

Your domain.
When the problem began.
What changed before the problem occurred.
The backup date you're considering.
What is currently broken.
Any error messages you are seeing.

Never provide your passwords or authentication codes in a support ticket.

A careful restoration can often save hours of rebuilding work. The key is choosing the right backup and understanding what will be replaced before you begin.

Preguntes Freqüents - FAQ

Categories

Categories