Backup and Data Protection
Backups are included with every server. They're your safety net: if something goes wrong, restore
Each server includes backups. They are your safety net: if an update goes wrong, someone deletes something they shouldn't, or ransomware gets in, you restore and keep going.
How backups work
Backups are made automatically, scheduled, without you having to remember: every hour, every day and every week.
They are configured per disk and per server, and the retention — how long you keep each backup — is configurable.
📘 Scheduled backup vs. snapshot
The backup is automatic and saves versions of your disks according to the schedule.
The snapshot is a manual snapshot of the entire machine that you take at a specific moment — for example, just before a risky change — so you can roll back if something goes wrong.
Ransomware protection
Your backups are stored as read-only copies: once created, they cannot be modified or encrypted from the server. If ransomware reaches the machine, it can't touch the backups, and you have somewhere to restore from.
You control and restore
We include and run the backup engine; you decide the schedules and retention, and you restore when needed. It fits the shared responsibility model: the infrastructure is ours, the control of your backups is yours.
The step-by-step guide to configure backups, create a snapshot, or restore is in How-to.
Backup is not high availability
🚧 Backup recovers; it does not keep things running
Backup is your safety net to recover data and state. Keeping the service available when a machine goes down is something else: continuity design, with multiple servers and the right architecture.
Backup and continuity complement each other, they do not replace each other.
Next steps
Configure backups, create a snapshot, or restore in How-to.
Review what you operate and what we operate in What is a Server?.
Last updated
Was this helpful?

