The risks of restoring a backup

Introduction

Restoring a backup can solve many problems, but it also carries risks. A backup copy returns the website or account to an earlier state, so everything created after that date may be lost.

Before requesting or performing a restore, it is important to understand what will be replaced.

What restoring a backup means

Restoring a backup means recovering files, databases, emails or settings from an earlier copy.

It can be done for:

• The whole hosting account.
• Files only.
• One database only.
• A specific folder.
• Emails.
• Specific settings.

The broader the restore, the greater the potential impact.

Main risks of restoring a backup

1. Loss of recent changes

If you restore a Monday copy, everything created afterward could disappear.

Examples:

• New orders.
• Comments.
• Published posts.
• Added products.
• Registered users.
• Design changes.
• Received forms.

2. Loss of emails

If the entire account is restored, it may affect emails received or sent after the backup date, depending on the type of restore.

3. Returning to a vulnerable version

If the backup contains outdated WordPress, plugins or themes, you could restore a website that was already insecure.

4. Reintroducing malware

If the copy was already infected, restoring it will not solve the problem. It may even bring malicious files back.

5. Overwriting files that are working correctly

Restoring without review may replace current files that are functioning properly.

6. Incompatibilities

If the PHP version, plugins or database changed after the backup, the restored copy may not work the same way.

What to review before restoring

Before restoring:

1. Identify when the problem started.
2. Choose a copy from before that date.
3. Decide whether you need to restore everything or only part of it.
4. Make a copy of the current state.
5. Inform users or customers if the website receives orders or registrations.
6. Review whether there are recent emails you need to keep.
7. Confirm that the copy does not contain malware.

When it makes sense to restore

It may be advisable if:

• You deleted important files.
• An update broke the website.
• A database was damaged.
• The website was modified by mistake.
• You need to go back to an earlier version.
• A clean backup exists from before an infection.

When you should not restore immediately

Avoid restoring without analysis if:

• You do not know when the problem started.
• The website is a store with recent orders.
• The copy could be infected.
• Only one plugin or one specific table is failing.
• You do not have a copy of the current state.

Useful tips

• Ask to restore only what is necessary.
• Keep a copy of the current state.
• Write down the date of the chosen backup.
• Review the whole website after restoring.
• Update the CMS and plugins after restoring.
• Change passwords if there was a hack.
• Verify forms, payments and emails.

Common problems

I restored the backup and orders disappeared

The copy was older than those orders. Full restores need special care in online stores.

I restored the backup and the hack came back

The restored copy was already infected or an active backdoor was left behind.

I restored the files but not the database

If the website depends on the database, you may need to restore both parts in a coordinated way.

Frequently asked questions

Does restoring a backup erase the current data

It can overwrite current data with older data. It depends on the type of restore.

Can I restore only one folder

In many cases, yes. Specify exactly which folder or file you need to recover.

Should I make a backup before restoring

Yes. It is advisable to save the current state before any restore.

Which date should I choose

The most recent date before the problem started.

Conclusion

Restoring a backup can save your website, but it must be done carefully. Before restoring, confirm the date, the scope and the risks so you do not lose recent data or bring back a vulnerable version.