BountySite performs quick restore by restoring only changes and not full site, making restores very simple and fast. Also BountySite revisions website files and database individually, giving more granular control on restores.

In previous blog, we saw how differential backup runs on BountySite. We saw that a new file virus.txt being added to the site, which has been tagged malicious. Lets do a site restore to get rid of the virus.

If you are performing a quick restore, then the latest version has the malware, and the previous version is what we need to revert back to. In this case, I deliberately(for demonstration) make a small change to site and let backup run, to create another revision. We will go to File Browser page, which shows site change summary(Sidebar -> Manage sites and backup -> File Browser).

Site change history for web

Do note that the Type is set to Web and not database. Here we see three revisions, and to be able to view changes, we click on View to see changes made for that backup.

Revision to restore to

So, we find that revision "2019-02-02 12:02:27 UTC", is the one which had backed up /virus.txt, which was tagged malicious file. Now the previous revision is 2019-02-02 10:00:38 UTC, which is the pristine version to restore to. We will go back to previous page to perform a restore.

Pristine revision

We will now click on Restore button to restore the live site to this revision. Post click, we get a Temporary error page, which may be error or just backup running warning). In this case, it is clearly the running backup.

Cant view this page while backup is running

BountySite first initiates a backup and then schedules a restore to the requested revision. We dont want to miss any latest changes on site. Now, we can check logs to see some restore details. Also, do note that this is a file restore only, and not database. In this case, we know that the malware is in a file, which needs to be deleted, and hence are not concerned about database. It is time to check the logs(Sidebar -> Logs -> Backup Log).

Restore details

We see only few files being touched:-

  • wp-blog-header.php has been marked for modification, which in this case is removal of comments
  • emptydir is a folder which I created for testing.
  • virus.txt file is marked for deletion

The restore only touched few files, without going through all files of the sites, and hence the restore was completed within 11 seconds. Now going back to File Browser page, we see a new revision with FTPS Restore Manager as Backup Author.

Post restore

BountySite keeps latest site contents as master version. So, the current latest version and the restored revision have the same file contents.

You can also reset files and database together, with Easy Restore(Sidebar -> Manage sites and backup -> Easy Restore).

Easy Restore

Clicking on submit initiates a web file backup followed by file restore, and then DB backup followed by DB restore.

BountySite makes site restores incredibly simple.

So, you already have a server backup? huh!?

  • How easy it is to perform a restore?
  • How much time does it take to perform a restore?
  • How do you find out which file is malicious and needs to reverted? Or do you blindly revert back to a version that you assume is pristine?
  • What if your last server backup is not pristine? How do you even know that it is pristine?
  • Are you able to track file changes for every backup?

Do you really have a website backup? Think again!