VPS Backup: service terms and limits
This document sets out the technical parameters, limits, rotation rules and data retention terms of the VPS Backup service.
Technical limits at a glance
| Parameter | Value or limit | Note |
|---|---|---|
| Backup type | Full image of the system disk | File-level or partial restore is not supported |
| Data capture point | Start of the backup | The disk is captured at a single point in time; data not yet written to the disk is not included |
| Maximum restore points in storage | 10 backups per VPS | Includes both automatic and manual backups |
| Manual backup limit | 5 backups per 24 hours | Rolling 24-hour window from the first manual backup |
| Automatic backup intervals | Hourly, daily, weekly, monthly | Set in the backup plan settings |
| Retention after the plan is canceled | 6 calendar days | Automatic, permanent deletion on day 7 |
| Impact on a running VPS | No server downtime | The backup is taken from a running server without interrupting access to it |
| Data consistency | A single disk snapshot at the start of the backup (crash-consistent) | The backup reflects the disk state at the start of the backup. InnoDB and PostgreSQL databases bring their data into a consistent state automatically on startup |
| Impact during restore | Server stop, disk overwrite | The server is unavailable while the restore is in progress |
Rotation and deletion rules
Automatic rotation (FIFO)
- The system strictly enforces the restore point quota per server.
- When the quota is reached, creating any new backup (scheduled or manual) automatically and permanently deletes the oldest restore point (point #1).
- When you lower the number of backups to keep, the extra backups are deleted as soon as you save the new plan, starting with the oldest ones, regardless of their type (automatic or manual). Deleted backups cannot be recovered.
Lifecycle after cancellation
- After the plan is deleted, the backups stay frozen for 6 days.
- For 6 calendar days, the client can still restore the server or resume the subscription.
- 6 days after the add-on is canceled, the storage is cleared automatically. After that, support cannot recover the data.
Responsibilities and security
Provider responsibilities
- Keeping the isolated backup storage operational and available.
- Running automatic backups according to the schedule of an active, paid backup plan.
- Keeping restore points for 6 days after the service is canceled.
Client responsibilities
- Paying invoices on time so the service is not suspended.
- Keeping track of rotation (for example, understanding that with 10 backups kept, the 11th point replaces the 1st).
- Checking the list of restore points before lowering the number of backups to keep: extra backups are deleted immediately and permanently.
- Saving critical data outside the server before restoring from a restore point.
- Choosing a convenient way to prepare databases and write-heavy applications for a backup. A backup captures the data already written to the disk, while some recent changes may still be held in application memory. A regular dump, or shutting down the server from inside the OS before a manual backup, writes these changes to the disk, and the backup is fully consistent.