Skip to main contentLaunch offer: 10% off your first order of any service Browse services
Hylance
Programming3 min read

Website Backup: What to Save and What It Costs

Learn what a complete website backup should include, where to store it, how often to run it, and what setup costs on Hylance.

By the Hylance editorial team

Website Backup: What to Save and What It Costs

Key takeaways

  • A complete website backup has two parts, and neither replaces the other: your site files and images on one side, and the database on the other.
  • Keeping the backup on the same server puts it at risk if the server fails or is hacked; the practical rule is to keep an automatic backup off-server.
  • Active stores and platforms need daily database backups and weekly file backups, or backups before updates, with a restore test every two months.
  • On Hylance, setting up daily and weekly automatic off-server backups for your website starts at around SAR 60 (about $16) at the time of writing.

To create a reliable backup for your website or online store, keep two connected copies: the full site files and the database. Set up an automatic schedule that uploads backups to separate cloud storage outside your hosting server. After the schedule is in place, perform at least one restore test to make sure the backup will work in an emergency.

What should a complete backup include?

Many site owners only download the theme folder or export articles from the dashboard, then discover after a site failure that images, plugins, and payment gateway settings were never saved. A full backup that restores the site as it was should include four parts:

  • Database: contains pages, products, orders, customers, comments, and settings.
  • Media and uploaded files folder: product images, article images, and files uploaded by users.
  • Theme files, plugins, and source code: along with configuration files such as wp-config or environment variables, stored in a secure and encrypted place.
  • A log of recent changes: knowing which plugin or update happened before the failure speeds up diagnosis after restoration.

Where should backups be stored, and why is the same server not enough?

If you store the backup inside a folder on the same hosting account, any hard drive failure, account breach, or accidental deletion can wipe out both the site and its backup. The standard 3-2-1 rule means keeping three copies on two different media, with one copy off-site. For small websites, the easiest way to apply this is to connect automatic backups to independent cloud storage such as Amazon S3, Google Drive, or Backblaze B2.

Also make sure the backup is stored in an account you own, not only in the developer’s account. Turn on two-factor authentication for the storage account, and encrypt the backup if possible, so your database file or customer data is not exposed if a link leaks. It is also better to name folders by date so you can quickly identify the latest healthy backup.

What backup schedule makes sense: daily or weekly?

Not every website needs the same frequency. The right schedule depends on how quickly data changes on your site:

Site typeDatabase backupsFile and image backupsSuggested retention
Active online storeDaily, or every 12 hours during peak seasonsWeekly, plus before any updateAt least 30 days
Services website or blogEvery two days or weeklyWeekly or monthly30 to 60 days
Static company website with infrequent updatesMonthly, plus before any changeWith every design changeLatest 3 to 6 copies

Why is a backup not enough without a restore test?

A backup that has never been tested is just a file you do not know will work. Automatic backups sometimes stop because storage fills up or a connection token expires, or they create an incomplete database file because of a server timeout. So set a reminder every two months to review the latest backup log and test restoring one copy in a staging environment.

  • Check the size of the new file against the previous backup. Any sudden drop in size usually means missing tables or media.
  • Turn on email alerts for any backup failure so you find out the same day, not a month later.
  • Write down the restore steps on a single page for your team, along with the cloud storage link, so the first minutes of an outage are not wasted searching for accounts.

Common website backup mistakes

  • Relying on a backup plugin that stores files on the same server, then consumes storage and causes issues.
  • Updating the theme, plugins, or PHP without taking an immediate backup before clicking the update button.
  • Ignoring backup failure notifications for weeks until a real problem happens.
  • Leaving backup ZIP files in a public folder that can be accessed through the browser.

How much does backup setup cost on Hylance?

On Hylance, setting up daily and weekly automatic off-server backups for your website starts at around SAR 60 (about $16). Cloudflare protection starts at around SAR 60 (about $16), and monthly WordPress maintenance and support starts at around SAR 80 (about $21) at the time of writing. Your payment stays protected on Hylance until you confirm delivery. Before sending your request, prepare dashboard access for the developer and the cloud storage account where the backups will be stored in your name, and specify how many days you want backups to be kept.

Ready-made tech services for backing up and protecting your website

Frequently asked questions

Is the backup from my hosting company enough?

Relying only on hosting backups is risky, because some plans keep backups on the same server or retain only the last day or week. The service may also stop, or the account may be deleted because of a billing issue. Having an independent off-server backup under your control gives you extra protection.

What is the difference between file backups and database backups?

Files include themes, plugins, product images, and uploaded files, while the database stores articles, products, orders, user accounts, and settings. Restoring one without the other gives you an incomplete or broken site.

How do I make sure my backup actually works?

Run a restore test on a staging environment or a temporary sub-server every two months to make sure the file is not corrupted and that the site, images, and links work after restoration.

Ready to put this into practice?

Browse Programming & Tech services on Hylance and order what your business needs, with escrow that protects both sides. Or create an account and list your first service in minutes.

All Programming guides