Web Development15 min read•

Web Development Company in Pune: Website Backups and Disaster Recovery — What a Proper Setup Includes and How to Test It

What website backups should cover, how often to take them, where to store copies and how to run a restore test, with questions to ask a web development company in Pune.

#web development company in Pune#website backup#disaster recovery#website restore test

Web Development Company in Pune: Website Backups and Disaster Recovery — What a Proper Setup Includes and How to Test It

A proper website backup setup has four parts: a copy of both the files and the database, taken on a schedule that matches how often your site changes, stored somewhere other than the server it protects, and tested by actually restoring it. A backup you have never restored is a hope, not a plan. If you are hiring a web development company in Pune, or reviewing what your current one does, the most useful single question is: "When did you last restore this site from a backup, and how long did it take?" The rest of this guide explains what sits behind a good answer, in terms a business owner can check without being technical.

It is written for owners of business websites, online stores and NGO donation sites who have been told "backups are included" in a hosting or maintenance plan and want to know what that sentence should mean. We do not quote prices for backup services because they vary with site size and tooling, and we do not cite statistics about how often sites are lost. The reasoning below holds for any site.

Backup, recovery and "it is on the hosting panel" are three different things

People use three phrases as if they were one.

  • A backup is a copy of your site's data at a point in time.
  • A recovery is the act of putting that copy back so the live site works again. It involves the files, the database, the configuration, the domain and often an SSL certificate, and it is where most plans quietly fail.
  • A hosting panel snapshot is a copy kept by your hosting company, usually on the same infrastructure as the site. It is useful, but it is one copy in one place, controlled by one vendor.

When a vendor says "we take daily backups", ask which of the three they mean, because the answer changes what you can rely on.

What exactly needs to be backed up

For a WordPress site, WordPress's own administration documentation is clear that a complete backup has two parts: the site files and the database, and that you need both to fully restore a typical site (WordPress Advanced Administration Handbook: WordPress Backups). The files include core, themes, plugins, uploads and configuration such as wp-config.php. The database, usually MySQL or MariaDB, holds your pages, posts, orders, users and settings, and it lives outside the WordPress folder.

That split catches people out. A backup that copies only the website folder will restore a site with no content. A backup that exports only the database will restore content with no theme, plugins or uploaded images.

Beyond WordPress

The same logic applies to other builds, with different pieces.

  • Shopify and other hosted platforms. The platform keeps the software running, but you are still responsible for your own data. Export products, customers and orders on a schedule, and keep copies of theme code, custom scripts and any app configuration you cannot easily recreate. Ask what the platform lets you export and how often.
  • WooCommerce. Everything above, plus orders. A store can take orders all day, so a nightly backup can mean losing a day of orders. This is why frequency is a business decision, not a technical default.
  • Custom builds. Source code in version control, the production database, uploaded files, environment configuration, and the list of third-party keys and accounts the application depends on. Our guide on staging, Git deployment and rollback explains how code is kept recoverable; the database and uploads still need their own backups.
  • Email and DNS. Often forgotten. If your domain's DNS records disappear, a perfectly restored website is still unreachable. Keep a written copy of your DNS records.

The overlooked items

A short list of things that are not in the database or the web folder, and are painful to rebuild from memory:

  1. DNS records and the registrar login.
  2. The SSL certificate setup, or at least the knowledge of how it is issued.
  3. Cron jobs and scheduled tasks, such as order sync or reminder emails.
  4. Server-side configuration, such as redirect rules, PHP version and memory limits.
  5. API keys and webhook settings for payment, shipping, WhatsApp and CRM integrations, stored safely and not in a chat thread.
  6. The licence keys of paid plugins and themes.

Our article on what you should receive and own at website handover covers where these should be recorded at launch.

How often: tie frequency to what you can afford to lose

WordPress's documentation gives a simple starting point: for smaller sites with fewer posts, a weekly backup; for high-activity sites, daily; and always back up the database before an upgrade (WordPress Backups handbook). Treat that as a floor. The real question is the one disaster-recovery planners call the recovery point objective, in plain words: how much recent work can we afford to lose?

Site type Changes how often Sensible backup rhythm to discuss
Brochure site for a clinic or consultant A few edits a month Weekly full backup, plus one before every update
Business site with a blog Posts weekly Daily database, weekly files
WooCommerce or Shopify store Orders every day Database at least daily, more often in sale periods; order export in addition
NGO donation site Donations around campaigns and festivals Daily database, more often during campaigns, and a tested restore before each campaign

These are discussion starting points, not rules. A store that takes a hundred orders an hour in a sale needs a different answer from one that takes five a day. If your developer proposes a rhythm, ask them to explain it in terms of orders or donations you could lose between backups.

Before every change

Whatever the schedule, take a fresh backup immediately before plugin updates, theme changes, PHP upgrades, migrations and campaign launches. Most site disasters are self-inflicted by an update, not caused by a hacker. Our note on the WordPress 7.1.2 security release is an example of why updates cannot simply be postponed, which makes a pre-update backup the safety net that lets you update promptly.

Where the copies live: more than one place

WordPress's handbook advises keeping several recent copies, at least three to five, in different places. Storing backups only on the same server as the website defeats the purpose, because a server failure, a hosting account suspension or a ransomware infection can take both the site and its backups at once.

A widely used rule of thumb in the industry is often called 3-2-1: three copies of your data, on two different kinds of storage, with one copy kept off-site. It is a guideline rather than a legal standard, and you can apply it in proportion to your site's size. For a small business website, a practical version looks like this:

  • Copy 1: the live site.
  • Copy 2: a backup on the hosting provider's backup system.
  • Copy 3: an independent copy in a different provider's storage, such as a cloud storage bucket or drive that you own the account for.

That last point is important. If the only backups are in an account owned by your agency or hosting reseller, and the relationship ends, you may lose access to them. Ask that at least one backup copy is in storage you control.

Encrypt and restrict access

A backup contains everything the site contains, including customer and donor data. A leaked backup is a data leak. Store backups with access limited to named people, use strong credentials with two-step verification on the storage account, and ask whether backup files are encrypted. If your site holds personal data, the obligations under India's data protection law apply to backups too; see our guide to DPDP Act website compliance for the website-side picture.

Automated backups fail silently

An automatic backup job can stop working without any visible sign: a full disk, an expired storage credential, a plugin conflict, a changed password. WordPress's own documentation recommends that you back up the automatic backups manually once in a while to confirm the process works. We would go further and make it a calendar item.

A minimal monitoring routine:

  1. Notification on success and failure. The backup tool should email or message someone when a run completes or fails. A tool that only reports failures can fail to report that it failed.
  2. A monthly look at the backup list. Check that the newest backup is recent and its file size is plausible. A sudden drop to a tiny size usually means something was not copied.
  3. A log of who is responsible. Name the person, at your company or your agency, who looks at it.

Testing the restore: the part most people skip

The test is simple to describe and rarely done. Take a recent backup, restore it to a separate location, and check that the restored site works. A staging site, a spare subdomain or a local environment is ideal. Never test by overwriting the live site.

A restore drill you can ask for

Ask your web development company in Pune to run this once and send you the result, then repeat it at least once or twice a year and before any big campaign.

  1. Pick a backup at random, not the newest one.
  2. Restore files and database to a clean test environment.
  3. Check the home page, a few inner pages, the contact form, the search, and the admin login.
  4. For a store, place a test order. For a donation site, run a test donation in the payment provider's test mode.
  5. Check images and uploaded files, which are the most commonly missing items.
  6. Record how long the whole process took, from decision to a working site.
  7. Write down anything that surprised you, such as a missing setting or a manual step, and fix it in the documentation.

The time recorded in step 6 is your real recovery time, which is more honest than any promise on a quotation. If it took four hours with the developer who built the site, ask how long it would take with someone who did not.

Common restore failures

These are the things restore drills typically uncover:

  • Database restored but the site URL setting still points to the old address.
  • Files restored but a hidden file, such as .htaccess, was not included.
  • Backups that exclude large folders, such as the media library, to save space, without anyone noting it.
  • A backup plugin that stores the backup inside the website folder, so a full wipe removes both.
  • A backup that works only on the same server configuration, with no record of PHP and database versions.
  • Encrypted backups where nobody has the key.

Disaster scenarios and what each one needs

A recovery plan is easier to judge when you walk through concrete events.

What happened What you need to have Typical first move
A plugin update broke the site A backup from just before the update, or a staging copy Roll back the plugin or restore the previous backup
The site was hacked A clean backup from before the infection, and a way to find how it got in Restore to a clean copy, change all credentials, patch the hole
Hosting account suspended or provider failed An off-site backup you can access, and DNS records Restore to a new host and repoint DNS
Accidental deletion of pages or products Frequent database backups, or the ability to restore a single item Restore the item, or restore to staging and copy it back
Campaign traffic crashes the site Capacity planning, plus a quick way to scale or disable heavy features See our guide on readiness for traffic spikes
Domain expired or was transferred wrongly Registrar login, renewal reminders in your name Recover through the registrar

Notice that only some rows are solved by a file backup. Others depend on documentation, ownership and access, which is why disaster recovery is as much about paperwork as about technology.

If you suspect a breach

A backup is not the same as an incident response. If personal data may have been exposed, there are reporting and communication obligations, which depend on your business and the nature of the incident. Our article on CERT-In breach reporting for websites explains the website-side basics, and a lawyer should advise on your specific case. Restore the site only after the cause is understood, otherwise the same weakness may be exploited again. Basic hardening, such as the HTTP security headers we describe elsewhere, reduces the chance of repeat incidents but does not replace patching and access control.

Who is responsible: reading the "backups included" line

Many hosting plans and maintenance contracts say "backups included". Here are questions that turn that line into something checkable.

  1. What is backed up: files, database, or both? Are email and DNS covered?
  2. How often, and how many copies are kept for how long?
  3. Where are the copies stored, and can we get a copy ourselves?
  4. Who is notified if a backup fails?
  5. When was a restore last tested, and what was the recovery time?
  6. Is a restore included in the plan, or charged separately? Is there a time commitment for restoring?
  7. Are backups taken before updates, and who performs updates?
  8. What happens to backups if we end the contract?

If the answer to several of these is "we will check", that is information. It does not mean the vendor is dishonest; many simply have not been asked. It does mean you should not treat "backups included" as a guarantee.

Backups are also one of the items that belongs in a clear written agreement; our guide on contract ownership and warranty for web projects lists what to settle in writing, and our maintenance and support guide describes what an ongoing plan normally covers.

A practical setup by site size

Small business or brochure site

  • A WordPress backup plugin or hosting-level backup, running weekly, with a copy sent to storage you own.
  • A manual full backup before every update.
  • A written note of DNS records and logins.
  • One restore test a year.

Online store

  • Daily database backup, with extra copies during sale periods.
  • Weekly file backup and a backup before each update.
  • A regular export of orders and customers from the platform, kept as a separate copy.
  • An off-site copy, and a restore drill to a staging site before the biggest sale of the year.
  • A documented list of integrations and their keys.

NGO or donation site

  • Daily database backups and more frequent ones during campaigns.
  • Care with donor data: encrypted storage and restricted access.
  • A tested restore before every major campaign, since a failure during a festival or appeal week is costly.
  • Documentation of how receipts, payment webhooks and the donor database are connected, so a restored site reconnects correctly. Our guide on donation site security and hosting covers the hosting side.

What a web development company should hand you

Ask for a one-page document, in plain language, that you keep outside the agency's systems. A good version includes:

  • What is backed up, how often, and where.
  • Who can restore, and how to reach them.
  • The measured recovery time from the last drill.
  • DNS and domain details and who owns each account.
  • A list of integrations and which accounts they belong to.
  • Steps to follow if the site is down, in order.

That is not a heavy document. It is what lets you or a replacement developer act calmly on a bad day.

Working with Govindani Infotech on backups and recovery

Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We build and maintain business sites, e-commerce stores, CRM systems and NGO donation platforms, and recovery planning is part of how we think about a build, not an add-on.

If you are unsure what your current backup arrangement actually covers, the most useful step is a short review: tell us your platform and hosting, and we will walk through the questions above with you and say plainly where the gaps are, before any price is discussed. For a new project, our website creation service page describes how we plan builds. You can message us on WhatsApp at wa.me/919201958278 or write through our contact page.

Frequently Asked Questions

How often should I back up my website?

It depends on how much you can afford to lose. A brochure site that changes monthly can be backed up weekly, while a store or donation site should have its database backed up at least daily. Always take a fresh backup before updates or migrations.

What is the difference between a website backup and a restore?

A backup is a saved copy of your site's files and database. A restore is putting that copy back so the site works again. Backups are only useful if restoring works, so ask for a restore test, not just proof that backups exist.

Where should website backups be stored?

In more than one place, and not only on the same server as the site. Keep at least one copy off-site, in an account you own, so a server failure, hosting suspension or ransomware infection does not take the site and its backups together.

Does my hosting company's backup mean I am covered?

Not entirely. Hosting backups are one copy, on the vendor's systems, with terms set by the vendor. Check how long copies are kept, whether restores are included, and whether you can download a copy yourself. Add an independent copy to be safe.

How do I test a website restore without risking the live site?

Restore a recent backup to a separate staging site or spare subdomain, then check pages, forms, login, images and, for a store, a test order. Time the process and note any manual steps. Never test by overwriting the live site.

Sources: WordPress Advanced Administration Handbook: WordPress Backups. The 3-2-1 description above is a general industry rule of thumb, not a quotation from that source.

Need Help With Your Digital Strategy?

Govindani Infotech helps Indian businesses and NGOs build websites, run ads, and grow online. Contact us for a free consultation.