Yandex Cloud Backup overview
Created VM backups are application-consistent: both data stored on disks and intermediate data of running applications (in-memory data and active reads and writes to disks) are saved. This approach lets you resume applications that were running at backup creation immediately after restoring your VM. This is important for VMs that are part of data storage systems, such as when a DBMS is running on the VM.
Cloud Backup can create full and incremental backups. A full backup stores complete data of a VM. This is reliable, but full backups take a lot of space and restoring VMs from them is more time-consuming. Incremental backups only contain data that differs from that of previous VM backups. This lets you save space and time for VM recovery. However, if any backup in the chain is damaged, you won't be able to restore your VM.
To be able to enable backups for your instance, when creating the instance, you need to connect it to the service and configure it. For more information, see Connecting Compute Cloud instances to Cloud Backup.
Once you have connected your instance to Cloud Backup and set it up, you need to link it to a backup policy that is, to a Cloud Backup resource. The policy includes settings for creating and storing backups. You can link your instances to default policies or create custom policies.
The service has restrictions — quotas and limits.
Comparison with disk snapshots in Compute Cloud
|Disk snapshots in Compute Cloud||Cloud Backup|
Only data written to disk before creating a backup is saved.
First all active reads and writes are terminated and then all disk and in-memory data is saved.
|Granularity||Disk||VMs with all disks.
We also plan to add support for VM application backups.
|Disk types||Network SSD and HDD||Any:
Network SSD and HDD,
and local disks on dedicated hosts
|Application awareness||No||To be implemented|
|Pricing||Per disk||Per VM|
Service activation and backup provider
Cloud Backup is enabled by a backup provider. Currently, the service only has one provider available: Cyberprotect.
If you got access to Cloud Backup, to get started, you need to activate the service, that is, to connect to a backup provider. You can activate the service directly on its page in the management console (see the getting started tutorial) or connect your first VM to Cloud Backup: the service will activate automatically in this case.
The minimum folder role required for activating the service is
backup.editor (see the role description).