> ## Documentation Index
> Fetch the complete documentation index at: https://docs.edbb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backups

> You are responsible for creating backups! Ensure you manage your machines and regularly backup your servers and all your important data!

## Protecting Your VPS Data

EDBB does not provide any backup services for VPS. \
It is important that you manage your own backups to protect your data.

## **What this means for you**

🛡 **You are responsible** for creating backups of your server and all important data. \
🛡 We recommend scheduling regular backups to ensure your data is safe.

### **Why Regular Backups Are Essential for Your VPS Data Protection**

> Regular backups are essential for protecting your data against hardware failures, accidental deletions, or cyber threats. Without proper backups, you risk losing critical data, leading to costly downtime or permanent data loss. By scheduling regular backups, you safeguard your systems, enabling quick recovery and uninterrupted operations, minimizing significant disruptions.

## Why It Matters

<CardGroup cols={3}>
  <Card title="🛡️ You Own the Recovery Plan">
    Operating system files, application configs, and customer data are your responsibility. Schedule backups before you need them.
  </Card>

  <Card title="⚡ Incidents Happen">
    Hardware faults, accidental deletes, or security breaches can strike without warning. Prepared backups mean rapid recovery.
  </Card>

  <Card title="🌍 Off-Site Saves the Day">
    Keep at least one copy outside the VPS—object storage, another data centre, or your own infrastructure.
  </Card>
</CardGroup>

***

## Build a Simple and Reliable Backup Plan

Having regular backups makes sure you can recover your VPS fast — even after system crashes, mistakes, or attacks.

<Steps>
  <Step title="1. Pick your backup type">
    Choose the method that best fits your setup:

    * **Full snapshots:** save the whole server or disk. Best for complete restores.\
      Tools: <code>
      dd</code>

      , <code>
      qemu-img</code>

      , or hosting snapshots.
    * **File backups:** copy only selected files or folders. Great for websites, configs, and databases.\
      Tools: <code>
      tar</code>

      , <code>
      rsync</code>

      .
    * **Cloud or incremental backups:** keep changes synced to remote storage for safety.\
      Tools: <code>
      rclone</code>

      , <code>
      restic</code>

      , <code>
      borg</code>

      .
  </Step>

  <Step title="2. Automate your backups">
    Backups you run manually are easy to forget — automate them with cron or systemd timers.

    **Example (runs every day at 2:30 AM):**

    ```bash theme={"system"}
    crontab -e
    ```

    Then add:

    ```bash theme={"system"}
    30 2 * * * /usr/local/bin/backup.sh >> /var/log/backup.log 2>&1
    ```

    You can also sync your files automatically to cloud storage or another VPS:

    ```bash theme={"system"}
    rclone sync /var/www remote:backups/server1 --exclude "cache/**"
    ```
  </Step>

  <Step title="3. Check and clean your backups">
    A backup only helps if it actually works.

    * **Check file hashes:** use SHA256 or MD5 to verify backups are valid.
    * **Test restores:** try extracting or mounting backups in a test folder.
    * **Clean up old files:** delete backups older than 30 days.

      ```bash theme={"system"}
      find /backups -type f -mtime +30 -delete
      ```
  </Step>

  <Step title="4. Keep a copy somewhere safe">
    Don’t store all backups on one machine.

    * Keep one local copy for quick recovery.
    * Upload another to external or cloud storage (S3, Backblaze, Google Drive, etc.).
    * Encrypt files before upload using <code>
      gpg</code>

      or <code>
      restic --password-command</code>

      .

    💡 *Tip:* Follow the **3-2-1 rule** — 3 copies, 2 different places, 1 offsite.
  </Step>
</Steps>

***

✅ A simple, automated backup plan keeps your server safe and restorable — no matter what goes wrong.

***

## Requesting a Downloadable Image

<Info>
  Instant snapshots are not included, but you can request a downloadable <code>
  .qcow2</code>

  image of your VPS disk. Each export costs <strong>€25</strong>
  to cover handling.
</Info>

* Contact Support via the portal messenger or by email with the VPS ID and timeframe.
* We prepare the image and provide a secure download link.
* Download promptly—links expire to keep data safe.

Full instructions live in [Requesting a Downloadable .qcow2 Image Backup](https://docs.edbb.com/faq/upgrades-downgrades/requesting-qcow2-image-backup).