| What you can back up for | Cloud server network disks | Cloud server network and local disks | Cloud server network disks |
|---|
| How backups are performed | - automatic — you must create a backup schedule plan;
- manually
| Manually | Manually |
|---|
| Types of backups | - full — when automatically scheduled and manually created;
- incremental — only when scheduled
| Full | Full |
|---|
| How to back up | You do not need to shut down the server or install software to create a backup.
You can: - configure in the Control Panel a schedule for automatic backups. Scheduled snapshots of the disk will be created and transferred to the backup repository. For more information, see Configure scheduled backups;
- create a backup manually in the Control Panel. For more information, see Create a backup manually
| Before creating an image, we recommend shutting down the server.
Create a disk image in the Control Panel or through the OpenStack CLI. For more information see Create an image from disk | Creating a snapshot does not require shutting down the server and installing software.
Create a snapshot of the disk in the Control Panel or through the OpenStack CLI. For more information, see Create a snapshot |
|---|
| How to restore a backup | When restoring 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 the entire disk from a backup | The created image is stored in the image store — you can create a cloud server or network disk from it | You can create a cloud server, network disk, or image from a snapshot |
|---|
| How many backups can be stored simultaneously | - If backups are created automatically on a schedule, the total number of backups in a cloud platform project is unlimited. You cannot create more than ten full backups or five chains of incremental backups of one disk within one plan;
- if backups are created manually, no more than 1000 backups in one project
| The number is limited only by project limits on images — these can be increased through technical support | No more than five snapshots per disk |
|---|
| Storage reliability | Backups are stored with triple replication on Servercore servers separately from disks, but in the same pool segment. You cannot change the storage location | Stored on Servercore servers separately from disks, but in the same pool segment. You can't choose where you want to store it. To improve storage reliability, you can move the image to another pool segment or download it and move it to a third-party infrastructure outside of Servercore | Stored on the same hardware as the disks — so a snapshot is not a full backup. The snapshot is always deleted along with the disk |
|---|
| Can you download a backup | ✗ | ✓ | ✗ |
|---|
| Alerts and monitoring | Copies that failed are displayed in the interface with the status ERROR | Images that failed, are displayed in the interface with the status ERROR | ✗ |
|---|
| Automatic backup consistency and health check | ✗
We recommend that you check the consistency and health of your backups manually through restoring from backup | ✗ | ✗ |
|---|
| Cost | Each GB of backups stored is charged. Storage prices can be viewed at servercore.com | Each GB of stored images is paid 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 was created. Prices for disks can be viewed at servercore.com |
|---|