Knowledge base

Snapshots, backups and the firewall on your cloud server

Take and restore snapshots, switch on daily backups, set firewall rules without locking yourself out, and rebuild a cloud server from its page.

Every cloud server has its own page under Servers. This article covers four things on that page: snapshots, automatic backups, the firewall, and rebuilding the server.

Snapshots: a copy you take yourself

A snapshot is a copy of the server's whole disk, taken when you click Take a snapshot. Take one before anything risky, such as an operating-system upgrade or a new PHP version. Add a short note so you can tell later what it was for.

  • A snapshot is kept until you delete it. Nothing deletes it for you.
  • It uses storage for as long as it exists. Its size and monthly figure appear beside it once it
  • has finished, which takes a few minutes.

  • Restore puts the server's disk back to the moment of that snapshot. Everything written to
  • the disk since then is lost, and there is no undo, so take a fresh snapshot first if you might need today's state. You can only restore a snapshot taken from the same server.

Automatic backups: copies taken for you every day

Switch on Backups and a copy of the server is taken every day. Older restore points are removed automatically, and the card shows how many are kept.

  • The card shows the monthly figure before you switch backups on.
  • ⚠️ Switching backups off deletes the restore points that already exist. They cannot be
  • brought back, so take a snapshot first if you want to keep the latest one.

The firewall

The Firewall card decides which traffic may reach the server. Each rule names a direction (incoming or outgoing), a protocol, a port or range of ports, and the addresses it applies to.

  • A firewall with no incoming rules blocks everything coming in, SSH included.
  • Before you save, check that a rule still lets you in: keep port 22 (SSH) open to your own
  • address. If you lock yourself out and the server has a Console card, it still opens a terminal on the server.

  • Rules are checked before anything changes. A rule we cannot apply is refused with the reason,
  • and the old rules stay in place.

Rebuilding (reinstalling) the server

Rebuild this server erases the disk and installs a clean operating system of your choice. The server keeps its plan. On some servers a rebuild or a restore swaps the disk in several steps and takes a few minutes. The page shows it as in progress, and you can close the page while it runs.

If a rebuild or restore cannot run at that moment, you are told so and nothing changes. Try again shortly.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →