| What backups can be created for | Cloud server network volumes | Cloud server network and local volumes | Cloud server network volumes |
|---|
| How backups are performed | - automatically — you need to create a plan with a backup schedule;
- manually
| Manually | Manually |
|---|
| Backup types | - full — when created automatically by schedule or manually;
- incremental — only when created by schedule
| Full | Full |
|---|
| How to create a backup | You do not need to turn off the server or install software to create a backup.
You can: - set up a schedule for automatic backup creation in the Control panel. According to the schedule, instant snapshots of the volume will be created and transferred to the backup storage;
- create a backup manually in the Control panel
| We recommend turning off the server before creating an image.
Create an image from a volume in the Control panel or via OpenStack CLI | You do not need to turn off the server or install software to create a snapshot.
Create a snapshot of a volume in the Control panel or via OpenStack CLI |
|---|
| How to restore a backup | When you restore from a backup, a new volume is created — you can connect it to an existing server, or use it to create a new cloud server, network volume, or image. You can only restore a full volume from a backup | The created image is stored in the image storage — you can create a cloud server or network volume from it | You can create a cloud server, network volume, or image from a snapshot |
|---|
| How many backups can be stored simultaneously | - if backups are created automatically by schedule, the total number of backups in a project is unlimited. You cannot create more than 90 full backups or 14 chains of incremental backups for one volume within a single plan;
- if backups are created manually, no more than 1 000 backups in one project
| The quantity is limited only by project quotas for images — these can be increased through technical support | No more than five snapshots for one volume |
|---|
| Storage reliability | Backups are stored with triple replication on Servercore servers, separate from volumes, but within the same pool segment. You cannot change the storage location | They are stored on Servercore servers separate from volumes, but in the same pool segment. You cannot choose the storage location. To increase storage reliability, you can transfer an image to another pool segment or download it and transfer it to third-party infrastructure outside Servercore | They are stored on the same hardware as the volumes — therefore, a snapshot is not a full-fledged backup. A snapshot is always deleted together with the volume |
|---|
| Can a backup be downloaded | ✗ | ✓ | ✗ |
|---|
| Alerts and monitoring | Copies that failed to be created are displayed in the interface with the ERROR status | Images that failed to be created are displayed in the interface with the ERROR status | ✗ |
|---|
| Automatic check for backup consistency and health | ✗
We recommend checking the integrity and health of copies manually by recovering from a backup | ✗ | ✗ |
|---|
| Pricing | You are charged per each GB of stored backups. Pricing for storage can be viewed on servercore.com | You are charged per each GB of stored images. Pricing for storage can be viewed on servercore.com | The cost of storing a snapshot is equal to the cost of the volume from which it was created. Pricing for volumes can be viewed on servercore.com |
|---|