VPSie home
Services

Backup for servers and volumes

Scheduled and on-demand copies of your servers, kept off the host, with snapshots for quick rollbacks and restore down to a single file.

Day 1TodayBackup copy in another locationRestore a server or one fileDay 1TodayBackup copy in another locationRestore a server or one file

Copies of your servers, kept away from the server

VPSie Backup stores full copies of your virtual machines and containers on a backup server, outside the host that runs them. You can back up on demand, every day, or on a schedule you define, and restore to the same server or to a new one.

  • Managed from the same console as your servers
  • Only changed data is sent after the first backup
  • Restore a whole server, or a single file
  • Snapshots for quick rollbacks, backups for real protection
Primary siteRecovery siteReplicationFailoverTested recovery planReplicationPrimary siteRecovery siteFailoverTested recovery plan

Four ways to protect a server

Pick per server. They can be combined.

Manual

On-demand backup

A full VM-level backup you start yourself, from the Recovery page or the server settings. Name it or accept a generated name.

Daily

Automatic backup

Turn it on for a server and it is backed up daily. Restore it in place or clone it as a new server.

Scheduled

Backup policy

Choose daily, weekly or monthly, set the occurrence and how many copies to keep, and attach it to one server or many.

Cross-site

Global backup

Regular backups stay in their data center. A global backup can be restored as a new server in the same data center, or cloned to another.

Snapshots are not backups

A snapshot is quick and good before a change. It lives with the server, so do not rely on it alone.

Server snapshots

Capture a server state with a name and a note, then roll back, rename or delete from the snapshots panel. A snapshot can carry an expiry date and is removed when it is due.

Storage snapshots

A recovery point on a shared volume instead of a server. Revert a database volume, or clone it and attach it to another server.

Schedules with limits

Policies run from a 5-minute scheduler. Minimum intervals are 1 hour on RBD-type, ZFS and LVM-thin storage and 4 hours on qcow2 and directory storage.

SnapshotSame place as the serverserver + its snapshotQuick, good before a changedo not rely on it aloneBackupServerKept awaySchedules, retentionProtect from deletionA separate copy of the serverQuick, good before a changedo not rely on it aloneServerSchedules, retentionProtect from deletionA separate copy of the serverSnapshotBackupKept awaySame place as the serverserver + its snapshot
A snapshot lives with the server. A backup is kept away.
Full copyNext copy: changed blocks onlySmall, fast backupFull copyNext copy: changed blocks onlySmall, fast backup

A backup engine built for repeat copies

The backup server is a client-server appliance. It reads only what changed, removes duplicate data, compresses it, and verifies it.

  • Incremental, deduplicated backups; running VMs use dirty-bitmap tracking for fast increments
  • Zstandard compression before the data leaves the host
  • SHA-256 checksums with scheduled verification jobs to catch bit rot
  • Sync datastores to another location, sending only the changes
  • Tape backup support; web interface, CLI and REST API

Getting data back

Restore options are chosen for stressful moments.

Whole server

Restore over the original or clone to a new server. Live restore starts the server while the data is still coming back.

Single file

Browse the contents of a VM or container backup, find the file, and restore it or download it as a ZIP or compressed tar archive.

Pause, protect, review

You can pause a policy, protect a backup so retention never deletes it, and see each server's next run and last result with a failure email if one fails.

Built to survive a bad day

Backups are a target in a ransomware attack, so they get their own controls.

Client-side encryption

AES-256-GCM encryption can be applied before data reaches the server. The key can be printed and stored in a vault.

Restricted by default

New users and API tokens have no permissions. Roles are explicit, tokens can be limited to one datastore, and two-factor sign-in is available.

Off-site copies

Existing blocks are not rewritten, and off-server, off-site sync gives you a copy that an attacker on the main system cannot reach.

Questions before you start

Is a snapshot a backup?

No. A snapshot keeps a server state for quick rollback and stays tied to the server. A backup is a separate copy on a backup server.

How often can I back up?

Policies set daily, weekly or monthly runs with a retention count. Where storage allows, the scheduler supports intervals down to one hour. Confirm what your storage class allows.

Where are backups stored?

On the backup server, outside the host. A global backup can be restored in another data center. Ask which data centers you can pick.

Can I restore just one file?

Yes, for VM and container backups. Browse the archive, then restore or download the file.

Does it cover servers that are not on VPSie?

Protecting other platforms is part of VPSie Protect. See the recovery and migration pages, or ask us.

Is backup included?

Pricing is shown in the console. Some license packages include it, so ask before you assume.

Learn more: On-demand backups Automatic backups Backup policies Ransomware-safe buckets

Back up what you cannot rebuild

Start with one server, then add policies as you go.