Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Backup
    • All guides
    • Activating the service
    • Restoring the Cloud Backup agent
    • Viewing operations on service resources
    • Limiting RAM usage by the Cloud Backup agent
    • Viewing backup statistics
    • Setting up Monium alerts
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • Troubleshooting

In this article:

  • Q3 2026
  • Q2 2026
  • Q1 2026
  • Q4 2025
  • Q3 2025
  • Q2 2025
  • Q1 2025
  • Q4 2024
  • Q3 2024
  • Q2 2024
  • Q1 2024

Yandex Cloud Backup release notes

Written by
Yandex Cloud
Updated at November 10, 2026
View in Markdown
  • Q3 2026
  • Q2 2026
  • Q1 2026
  • Q4 2025
  • Q3 2025
  • Q2 2025
  • Q1 2025
  • Q4 2024
  • Q3 2024
  • Q2 2024
  • Q1 2024

Q3 2026Q3 2026

Starting August 17, 2026, a fee will be charged for backing up external resources in the Kazakhstan region.

Q2 2026Q2 2026

  • Introduced capabilities to connect VMs and servers located outside Yandex Cloud to Cloud Backup. For more information, see these docs:
    • Connecting VMs and servers from outside Yandex Cloud to Cloud Backup
    • Connecting a VM or server from outside Yandex Cloud to Cloud Backup
    • Creating a backup of a resource
    • Recovering an external VM or server from a backup
  • Streamlined the process for connecting an existing Compute Cloud VM to Cloud Backup in the management console: you no longer need to attach a service account to the VM or manually install the Cloud Backup agent.
  • Added Identity and Access Management access policies to enforce restrictions on certain actions with Cloud Backup resources even if such actions are allowed by user roles.

Q1 2026Q1 2026

  • Improved the process for creating a VM with a connection to Cloud Backup in the management console.
  • Added the backup.auditor role.

Q4 2025Q4 2025

  • Implemented the ability to create, via the management console, a VM connected to Cloud Backup without linking a service account.

  • Added support for new backup policy settings:

    • pre-data capture command "prePostCommands":"type":"PRE_DATA_COMMAND"
    • post-data capture command "prePostCommands":"type":"POST_DATA_COMMAND"

    These are similar to the pre- and post-backup commands; however, they are executed as close as possible to the backup snapshot.

  • Added a quota for the number of BareMetal servers connected to Cloud Backup per cloud.

Q3 2025Q3 2025

  • Released the service for General Availability in the Kazakhstan region.
  • Updated the yc backup provider activate Yandex Cloud CLI command with a step requiring explicit confirmation of backup provider activation, as well as the --force flag for activation without confirmation.
  • Added new settings for backup policies:
    • Executing commands before and after taking a backup.
    • New run schedule type where you set the interval between the end and start of backups.
  • Added new Yandex Monitoring metrics:
    • agent_alive: Cloud Backup agent activity indicator.
    • agent_version_available: Availability indicator for a new Cloud Backup agent version.
    • error: Backup errors.

Q2 2025Q2 2025

  • Implemented automatic connection of Yandex BareMetal servers to Cloud Backup when ordering them from the management console.
  • Added new settings for backup policies:
    • Creating LVM snapshots.
    • Sector-by-sector backups.
    • Running skipped jobs after the VM or Yandex BareMetal server loads.
    • Checking backups.
  • Discontinued support for the preserveFileSecuritySettings and quiesceSnapshottingEnabled backup policy parameters.
  • Supported CentOS 7 for Yandex BareMetal servers.

Q1 2025Q1 2025

You can now use the Yandex Cloud CLI to delete all backups of a specific VM or Yandex BareMetal server.

Q4 2024Q4 2024

  • Added support for new operating systems:
    • For Yandex Compute Cloud VMs:
      • Debian 12.
      • Ubuntu 24.04 LTS.
    • For Yandex BareMetal servers:
      • Debian 10
      • Debian 11
      • Ubuntu 24.04 LTS
  • Added support for BareMetal server backup management in the management console.
  • Added new Yandex Cloud CLI features:
    • Viewing the parameters of backup disks and partitions.
    • Service activation.
    • Connecting and reconnecting a VM with OS Login.

Q3 2024Q3 2024

  • You can now add an existing backup policy when creating a VM connected to Cloud Backup from the management console, CLI, Terraform, and API.
  • Added support for a new data source in Terraform, yandex_backup_policy, to get information about a backup policy.
  • Added a new resource in Terraform, yandex_backup_policy_bindings, to link VMs to backup policies.
  • Implemented sending service metrics to Yandex Monitoring.
  • You can now create VM backups outside the backup policy schedule using the CLI.
  • Added support for Yandex BareMetal server backups.

Q2 2024Q2 2024

  • Updated the Cloud Backup agent.
  • Added support for new operating systems:
    • Ubuntu 22.04 LTS
    • Ubuntu 22.04 LTS OS Login
    • CentOS Stream
  • Added support for images with OS Login:
    • Ubuntu 20.04 LTS OS Login
    • Ubuntu 18.04 LTS OS Login
    • CentOS 7 OS Login
  • Added the listTasks REST API method for the Resource resource and the ResourceService/ListTasks gRPC API call. You can use them to view the backup activities of connected VMs.
  • Added the following parameters to the REST API methods for the Resource resource and to the ResourceService gRPC API calls:
    • initStatus: VM initialization status in Cloud Backup.
    • metadata: Metadata for detailed information about the VM registration process in Cloud Backup.
  • Added these events to the service's audit logs:
    • InitResource: Initializing a VM connection to Cloud Backup.
    • UpdateResource: Updating the status of a VM connection to Cloud Backup.

Q1 2024Q1 2024

  • In the management console, on the Operations tab, some inherently long-running tasks are now considered asynchronous operations, with a completion percentage added for certain actions.
  • Updated the process of applying changes for backup retention rules. By default, new rules will now take effect as soon as another backup is created.
  • Added support for creation of a policy with the scheduling.scheme=CUSTOM custom backup schedule scheme. For more information, see Backup policy specification.

Was the article helpful?

Previous
Audit Trails events
Next
Troubleshooting
© 2026 Direct Cursus Technology L.L.C.