| What you can create backups for | Cloud server network disks | Cloud server network and local disks | Cloud server network disks |
|---|
| How the backup is performed | - automatically — you need to create a plan with a backup schedule;
- manually
| Manually | Manually |
|---|
| Types of backups | - full — at automatic creation by schedule and manually;
- incremental — only when created by schedule
| Complete | Complete |
|---|
| How to create a backup | You do not need to shut down the server or install software to create a backup.
You can: - customize the schedule automatic backup creation in the control panel. Scheduled snapshots of the disk will be created and transferred to the backup storage;
- back up manually in the control panel
| We recommend shutting down the server before creating the image.
Create an image from the disk in the control panel or through the OpenStack CLI | You do not need to shut down the server or install software to create a snapshot.
Create a snapshot of the disk in the control panel or through the OpenStack CLI |
|---|
| How to restore a backup | When you restore from a backup, a new disk is created — you can connect it to an existing server, create a new cloud server, network disk, or image from it. You can only restore a full disk from a backup | The created image is stored in the image repository — you can create a cloud server or network drive from it | You can create a cloud server, network drive, or image from a snapshot |
|---|
| How many backups can be stored at the same time | - If backups are created automatically on a schedule, the total number of backups in the project is unlimited. You cannot create more than 90 full backups or 14 incremental backup chains of one disk within one plan;
- if backups are created manually, no more than 1000 backups in one project
| Quantities are limited only project limits on images — they can be enlarged through technical support | No more than five snapshots for one disk |
|---|
| Storage reliability | Backups are stored with triple replication on Servercore servers separate from disks, but in the same pool segment. The storage location cannot be changed | Stored on Servercore servers separately from disks, but in the same pool segment. You cannot select the storage location. To improve storage reliability, you can imprint to another pool segment or download it and move it to a third-party infrastructure outside of Servercore | Stored on the same hardware as disks — so a snapshot is not a full backup. A snapshot is always deleted along with the disk |
|---|
| Is it possible to download a backup | ✗ | ✓ | ✗ |
|---|
| Alerts and monitoring | Copies that could not be created are displayed in the interface with a status of ERROR | Images that could not be created are displayed in the interface with the status ERROR | ✗ |
|---|
| Automatic check of backup consistency and operability | ✗
We recommend checking the integrity and operability of the copies manually via restore from backup | ✗ | ✗ |
|---|
| Cost | Each GB of backups stored is paid for. Storage prices can be viewed at servercore.com | Each GB of stored images is charged for. Storage prices can be viewed at servercore.com | The cost of storing a snapshot is equal to the cost of the disk from which it is created. Disk prices can be viewed at servercore.com |
|---|