In this article9 sections
A website backup is only useful when you can restore it, and on Plesk the backup and the restore cover different things. A full server backup protects the whole machine. A website backup protects one domain: its files, its databases, its mailboxes and its settings. Most people only need the second, and most people never test it. This guide shows how to create a website backup in Plesk on Windows hosting, where to store it, how to restore a single website, and how to check the restore on a test domain before you need it.
SiteHarbour’s Windows hosting plans include free daily backups. Keep your own copy as well, so you can restore on your schedule and keep the copy off the server. The steps below cover both.
What a Plesk website backup contains
A website backup in Plesk holds the domain’s files, its MS SQL and MariaDB databases, its mailboxes if it has any, its DNS zone, and its subscription settings. It does not hold the server itself, the other websites, or the Windows configuration. The restore covers the same set, so a website restored to a new server needs the same plan and the same PHP or .NET runtime.
Step 1: Create a backup in Plesk
In Plesk, open Tools & Settings, then Backup Manager. Choose the option to back up a website, select the domain, and choose whether to include the mailboxes. Select Back Up.
Expected: a new backup file appears in the list with its date, size and the domain it holds. Check that the size is close to the size of the site’s files plus its databases. A file far smaller than expected means something was skipped.
Step 2: Download the backup to your own storage
Download the backup file, and keep a copy off the server. A backup on the same server is lost with it, and it is the first thing a compromised account would delete. Store the copy on a second computer or a storage service you control, and encrypt it if it holds customer data or mail. Keep at least one recent copy and one older copy.
Step 3: Restore into a test domain first
Restoring over a live site is the risky step, so do it first on a test domain. Create a subdomain such as test.example.com, then restore the backup into it from Backup Manager. Choose the restore target that names the test domain, not the live one.
Expected: the restore finishes without errors, and the test domain appears under Websites & Domains. Open the test domain in a browser and check the home page, a page that uses the database, and a file that was uploaded. A WordPress site should show the dashboard after a login.
Step 4: Check the databases
Open the restored databases in the Plesk database tools. Check that the tables are present and that the row counts look right. Compare a few recent records with what you expect to see. A restore can finish with a database that is missing tables, and the site then shows errors only on the pages that use them.
Step 5: Restore the live site
When the test restore passes, restore the live website. Put the site into maintenance mode first, or warn the users, because the restore replaces the current files and database. Take a fresh backup of the live site before you start, so you can undo the restore if it goes wrong. Then restore the backup into the live domain and check the same pages as in Step 3.
Check the SSL certificate after the restore. If the restore moved the domain to a new server, the certificate may need to be reinstalled, as described in how to create a website and install SSL in Plesk.
Step 6: Schedule the backups
A backup you make by hand is a backup you forget to make. In Backup Manager, set a schedule for the website backups, and choose how many copies to keep. A common setting is a daily backup kept for two weeks, and a weekly backup kept for two months. Adjust the numbers to the amount of data that changes, and to the space you have. The schedule runs on the server, so it works while you are away.
Common mistakes
- Never testing the restore. A backup that has never been restored is only a guess.
- Keeping every copy on the server. Keep one copy off the server.
- Restoring over the live site first. Restore to a test domain, check it, then restore the live one.
- Forgetting the databases. Check that the restore includes them, and open a table to see that it has rows.
- Skipping the certificate check. A restore to another server can leave the site without a valid certificate.
Frequently asked questions
Does a Plesk backup include the entire server?
No. It covers one website and its settings. Server-wide backups are a separate process that your host manages.
Can I restore one file instead of the whole site?
Yes. Open the backup in Backup Manager and choose the file or folder to restore, then check it on the live site.
How long does a restore take?
It depends on the size of the site and its databases. Large sites can take an hour or more. Plan the window before you start.
Is the free daily backup enough?
It is a useful safety net, but it should not be your only copy. Keep your own copy off the server, and test the restore on a schedule.
A website backup protects your site only if you can restore it. Create one in Backup Manager, download a copy off the server, restore it to a test domain, and check the database and the certificate before you touch the live site. Set a schedule so the backups keep running, and test the restore again every few months. For the deploy process that keeps the code in step with your backups, read how to deploy a website with Git in Plesk.