[Yandex Cloud documentation](../../index.md) > [Yandex Compute Cloud](../index.md) > [Concepts](index.md) > Backups

# Backups in Compute Cloud


Data contained in images, snapshots, and disks that are not attached to VMs is stored securely and replicated within the Yandex Cloud infrastructure.

To back up the data from disks attached to VMs, you need to create disk snapshots on a regular basis. You can do this both [manually](../operations/disk-control/create-snapshot.md) and automatically, [on schedule](snapshot-schedule.md).

To restore a VM from a disk snapshot, you can:
* Create a new disk from a snapshot, and then [attach the created disk](../operations/vm-control/vm-attach-disk.md) to a VM.
* Create a new VM [from a set of snapshots](../operations/vm-create/create-from-snapshots.md). In the operation parameters, you can specify both boot and regular disk snapshots.

You cannot recover a boot disk of an existing VM from a snapshot or image. However, you can create a new VM to recover a boot disk from a snapshot. To recover the boot disk of an existing VM, use [Yandex Cloud Backup](../../backup/index.md).


## Comparison with backups in Cloud Backup {#backup-comparison}

In Cloud Backup, you can create [full and incremental backups](../../backup/concepts/backup.md#types) of virtual machines along with boot disks and restore VMs from these backups. VM backups are application-consistent: they save not only the data stored on disks but also the data already sent but not yet fully written.

{% note info %}

If you use a policy with the `fastBackupEnabled` [option](../../backup/concepts/policy.md#specification) and ran an antivirus scan before creating an [incremental backup](../../backup/concepts/backup.md#types), the backup time may increase significantly. Read more in [Interaction with an antivirus](../../backup/concepts/av-interaction.md).

{% endnote %}

With Cloud Backup, you can [restore](../../backup/operations/backup-vm/recover-file-by-file.md) individual files and directories from a backup.

To enable backups on a VM, [connect](../../backup/concepts/vm-connection.md) the VM to Cloud Backup and [link](../../backup/operations/policy-vm/update.md#update-vm-list) it to a backup [policy](../../backup/concepts/policy.md). The provider must [support](https://docs.cyberprotect.ru/ru-RU/CyberBackupCloud/21.06/user/#supported-operating-systems-and-environments.html) the VM operating system.

| | Disk snapshots in Compute Cloud | Cloud Backup |
| --- | --- | --- |
| **Granularity** | Disk | VMs with all disks<br>Individual files and folders<br>VM applications (coming soon). |
| **Disk types** | All types except local disks on [dedicated hosts](dedicated-host.md).<br>The snapshot creation time is not fixed for [non-replicated disks and SSD-IO](disk.md#nr-disks). | All disk types |
| [**LVM**](../../backup/concepts/backup.md#lvm) | Not supported | Supported |
| **Recovery** | Full recovery to a new VM only. | To a new or existing VM.<br>Partial recovery of individual files. |
| **Consistency** | Atomic snapshot of each disk. | Atomic snapshot of the entire VM, individual folders, or files. |
| **Backup integrity checks** | Not supported | Supported |
| **Agent installation** | Not required | Required, installed automatically when connecting a VM to the service. |
| **Optimization** | Full backups only.<br>Data compression is not supported. | Full or incremental backups.<br>Multiple data compression levels with an option to opt out. |
| **Pricing** | Per GB of stored backups. | Per GB of stored backups and VM connection fee. |
| **Required VM status** | You can create a [snapshot](snapshot.md) on both stopped or running VMs. | You can only create a snapshot on a running VM with the [Cloud Backup agent](../../backup/concepts/agent.md) installed. |


## Use cases {#examples}

* [Backing up a VM with Hystax Acura Backup](../tutorials/hystax-backup.md)
* [Associating a Yandex Cloud Backup policy to a VM automatically](../../tutorials/archive/vm-with-backup-policy/index.md)