A backup on the server is handy, but not foolproof. If something goes wrong with the server itself, you’ll also want a copy on your own computer or in separate cloud storage. In this article you’ll read how to download a backup of your website and store it locally, which files you need, and how best to automate this.
Why a local backup in addition to your server backup
Most web hosting packages automatically create daily backups on the server. That’s a great safety net for a hacked site or a failed update. But a backup stored on the same infrastructure as your website doesn’t protect you against everything. Think of an account that gets accidentally cancelled, an outage at your hosting provider, or a mistake while migrating to another provider.
By regularly placing a copy locally or in separate cloud storage (such as Google Drive, Dropbox, or an external drive), you always have an independent backup. This takes little effort and prevents you from being completely dependent on one system.
Downloading a backup via Plesk
If you have hosting with Plesk as control panel, this is the fastest way to download a complete backup.
Log in to Plesk
Go to your Plesk environment and log in with your account details.
Open Backup Manager
Click on your domain and go to the Backup Manager section in the menu.
Create a new backup if necessary
If there’s no recent backup available, choose ‘Back up’ and wait until it’s ready.
Download the backup file
Click on the filename icon next to the backup to download the .tar or .zip file to your own computer.
Store the file in a safe place
Save the file locally or in cloud storage, separate from your hosting account.
Downloading a backup via FTP or a plugin
No Plesk or prefer separate files? Then you can also work via FTP or a plugin.
Via FTP: connect to your hosting account via an FTP program (such as FileZilla) and download the complete website folder to your computer. For the database, create a separate export via phpMyAdmin: select your database, go to the ‘Export’ tab, and download the SQL file.
Via a plugin (WordPress): install a backup plugin that supports exports to cloud storage, such as Google Drive or Dropbox. Such a plugin can automatically create the backup at a fixed time and write it away, without you having to think about it yourself.
Both methods work, but require you to store files and database separately. A backup is only complete if you have both components.
Storing local backups safely and clearly
Downloading a backup is one thing, keeping it usable is another. A few practical guidelines:
- Use clear filenames with a date, so you can quickly find the right version.
- Don’t just keep the latest backup, keep a few earlier versions as well.
- Don’t put sensitive backups (with customer data or passwords) unsecured in a shared cloud folder.
- Occasionally test whether a backup actually works by unpacking it locally and checking it.
If you still run into a problem, such as a corrupt file or a failed export, you’ll find more explanation in the knowledge base or you can contact the support department of your hosting provider.
Frequently asked questions
How often should I make a local backup?
That depends on how often your website changes. For a webshop or active blog, weekly is advisable, for a static website monthly is often sufficient.
Can I download only the database without files?
Yes, that’s possible via phpMyAdmin. Select your database and export it as an SQL file. Handy if only the content changes and the files remain the same.
Is a local backup a replacement for automatic backups on the server?
No, see it as a supplement. Automatic backups on the server can be restored quickly, a local copy is your safety net if something goes wrong with the server or the account itself.
Does this also work if I want to switch to another hosting provider?
Certainly, a local backup is even recommended before you move. You can read more about this at switching to Tandata.
Conclusion
A backup on the server is a good start, but a local copy prevents you from being completely dependent on one system. Regularly download your files and database, store them clearly, and occasionally test whether they still work. This way you’ll be well prepared for any unexpected problem.