Website Backup and Recovery Basics for Business Owners

A website backup is a saved copy of your site's pages, files and database that lets you restore it if something breaks, and a backup you have never tested is only a hope. The useful questions are how often copies are made, where they are stored, how long they are kept, and how quickly someone can put the site back. You do not need to be technical to ask these questions. You only need to know which ones matter.

What a website backup actually is

A website is usually made of two things. The first is the files: your pages, images, design and settings. The second is the database, which holds content such as page text, blog posts, enquiries and, on shops, orders. A complete backup captures both, so that restoring it brings back the site as it was at a particular moment.

Think of a backup as a dated photograph of the whole website. If the site is damaged on Wednesday, you can go back to the photograph from Tuesday night. You lose only what changed in between. How much that costs you depends on how often the photographs are taken, which is why frequency matters.

Some types of website hold very little that changes. A five-page company site that you update twice a year barely needs daily backups. A site that takes bookings or orders every hour changes constantly and needs much more frequent copies. Match the schedule to how often your site changes, not to a generic rule.

Why backups matter for a small business

Most owners think of hackers first. In practice, the common reasons to need a backup are more ordinary.

• Human error. Someone deletes a page, overwrites a file or publishes a half-finished edit.
• A bad update. A software update or plug-in change breaks the layout or the contact form.
• Hosting problems. A server fault, a billing lapse or a provider issue takes the site offline or loses data.
• Security incidents. Malware or unauthorised changes need a clean version to return to. Read our guide to website security basics for prevention.
• Moving house. Changing provider or redesigning is safer when you hold a full copy first.

Questions to ask your provider

Whether you pay a web agency, a hosting company or a monthly service, the answers should be clear and specific. Vague answers such as "yes, we do backups" are not enough. Our guide on website hosting in Singapore explains what different hosting arrangements usually include, and many of the same questions apply.

Put the answers in an email so there is a record. If the provider cannot answer, that is useful information. Ask too who owns the site and its files, because that decides whether you can take a copy with you. Our guide who owns your website explains what to look for in an agreement.

How often should backups run?

The right answer comes from one question: how much work can you afford to lose? If a backup runs nightly, the worst case is losing up to a day of changes. If it runs weekly, you could lose up to a week.

For a brochure site that you update occasionally, a regular automatic backup plus a copy before each change is usually sensible. For a site that collects bookings, enquiries or orders all day, more frequent copies matter, because every lost entry is a lost customer. Ask yourself what happens if you lose the last 24 hours, and let that decide.

Whatever the schedule, keep several past versions. A backup taken after a problem has already started only preserves the problem. Older copies let you go back to a version from before it began.

A simple rule for where to keep copies

A widely used rule of thumb is to keep three copies of anything important, on two different kinds of storage, with one copy kept somewhere else. You do not have to follow it to the letter, but it expresses the idea well: do not let a single failure be able to destroy everything.

If you manage your own login details, store them in a password manager shared with a trusted colleague, and make sure the hosting and domain accounts are in the business's name. Losing access is a recovery problem that no backup can fix. See our domain guide for that side of ownership.

How to test a recovery without drama

Many owners discover their backups do not work on the worst possible day. Testing removes that risk. You do not have to do the technical work yourself, but you should ask for evidence that a restore has been tried.

Repeat the test after major changes, such as a redesign or moving provider, and at least once a year. Record the result in your facts register so you know the date of the last proven recovery.

What to do when something goes wrong

Speed and calm matter more than cleverness. Have a plan before you need it, and keep it short enough to read under pressure.

If the incident involved customer personal data, you may have obligations under Singapore's data protection law. Our guide to PDPA for website owners gives a starting point, and a professional adviser can confirm what applies to you.

Backups are one layer, not the whole defence

Backups let you recover. They do not prevent the problem. Keep software and plug-ins updated, use strong and unique passwords, limit who has access, and keep only what you need on the site. If a provider handles these for you, ask what is included. Our page on website maintenance describes what ongoing care typically covers.

Next step

Send your provider the questions above this week and keep the reply. Then ask for a test restore and write down the date. If you are choosing a provider, compare what each includes and make sure recovery is covered. Website.sg builds and looks after custom websites for S$97 a month, with the domain bought separately in your own name and the option to cancel any time, but whichever route you choose, a tested backup is a good sign that a site is being looked after properly. You can see how we approach the build on our website development page.