---
title: Hosting Backups
description: Copies of files and databases for recovery after breakage or bad updates. Frequency, offsite storage, and tested restores beat brochure labels.
canonical: https://penasihathosting.com/en/hosting-wiki/hosting-backups
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# Hosting Backups

## Overview

- **Summary:** Copies of files and databases for recovery after breakage or bad updates. Frequency, offsite storage, and tested restores beat brochure labels.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**Hosting backups** are copies of files, databases, and (ideally) mail you can restore after breakage, hacks, or bad updates. A brochure checkbox is not enough — what matters is **what is copied, how often, where it lives, and whether restore was tested**.

Many site owners only think about backups when it is too late: a plugin update breaks checkout, or injected files overwrite the theme. A tested backup turns panic into a procedure.

## A Simple Analogy

A backup is a **spare house key plus a floor plan** stored off-site. Keeping the only copy in the same kitchen drawer (backup only on the same server) still fails if the house burns or the account is suspended.

## Common Types

| Type | Typical contents | Note |
| --- | --- | --- |
| **Files** | Document root, uploads | Without DB a CMS is empty |
| **Database** | MySQL/MariaDB | Required for WordPress |
| **Full account** | cPanel home + DBs | Convenient, heavier |
| **Offsite** | S3, Drive, your PC | Best against server loss |

## Sensible Practice

- Think 3-2-1: multiple copies, different media, one offsite  
- Do not rely on a single backup inside the same account ([inodes](/en/hosting-wiki/inode) can fill too)  
- Test a restore to a [subdomain](/en/hosting-wiki/subdomain) at least once  
- Before big theme/plugin upgrades: manual backup first  

[cPanel](/en/hosting-wiki/cpanel) often includes **Backup** / **JetBackup** — check daily/weekly retention and whether mail is included.

## What to Watch For

- Host “automatic backups” are not eternal guarantees — read retention  
- Untested backups are assumptions  
- Whoever holds the archive can read sensitive data  
- Huge on-account backups burn disk and inodes  
- Match frequency to how often content changes  

## FAQ

<Accordion>
  <AccordionItem title="My host says backups exist — am I safe?">
    Safer than nothing, but check frequency, retention, and whether databases are included. Keep your own offsite copy for critical data.
  </AccordionItem>
  <AccordionItem title="How often should I back up?">
    Busy sites: daily. Brochure sites: weekly may do. Always back up before major changes.
  </AccordionItem>
  <AccordionItem title="Backup vs staging?">
    Staging is for testing. Backup is for recovery. You want both mindsets; neither replaces the other.
  </AccordionItem>
  <AccordionItem title="Can someone download my backup files?">
    If they sit in the document root without protection, yes. Keep archives outside the web root or in private storage.
  </AccordionItem>
</Accordion>