English

বাংলা
हिन्दी

English

বাংলা
हिन्दी

Appearance

Backups, snapshots and reboot ​

This guide explains how to make your own backup of important files, what snapshots are and whether your plan offers them, how to reboot safely, and when a reinstall is possible.

Before you begin ​

  • SSH access, and the list of folders and databases that matter to you.
  • Confirmation from your plan about backups, snapshots and reinstall options. Not every VPS plan offers them.
  • Enough free disk space for the backup. See Resources and disk.

Do not assume a backup exists

Check the backup option in your plan and make your own copy before any risky change. A backup you have never tested is not proof that you can restore.

Steps ​

Make a backup of important files ​

  1. Choose the folders to back up, such as your website folder and your database export.

  2. Create a compressed archive, and save it in a different location from the original:

    bash
    sudo tar -czf /root/backup-$(date +%F).tar.gz /var/www/yourdomain

  3. Check that the archive exists and has a sensible size:

    bash
    ls -lh /root/backup-*.tar.gz

  4. Download a copy to your own computer if you need it off the server, and keep it private.

Snapshots ​

If your plan offers snapshots, create one before a major change, and check its status in the panel. Snapshots are a plan feature, so do not rely on them unless your plan lists them.

Reboot ​

  1. Warn anyone who uses the site, and make a backup first.

  2. Reboot the server:

    bash
    sudo reboot

  3. Wait a few minutes, then reconnect with SSH and check that your services are running.

Reinstall ​

A reinstall removes the data on the server. Use it only if your plan offers it, and only after a complete backup. Ask support if you are unsure.

Expected result ​

You have a tested backup of your important files, the server restarts cleanly, and your services start again.

If something goes wrong ​

  • The archive is missing or very small. Check the path and the free disk space, and run the command again.
  • The server does not come back after a reboot. Use the console or support options your plan provides, and contact support.
  • A service fails to start after a reboot. Check its status with sudo systemctl status, and read the error.

Last reviewed ​

2026-10-27