Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
  • Yandex Container Solution
    • Resource relationships
    • Graphics processing units (GPUs)
      • Overview
      • Disks
      • Disk snapshots
      • Creating scheduled snapshots
      • Non-replicated disk placement groups
      • File storages
      • Read and write operations
    • Images
    • Dedicated host
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Cron expressions
  • Possible field values
  • Special characters
  • Examples of cron expressions
  • Special expressions
  • Storing snapshots
  • Snapshot names
  • Schedule statuses
  1. Concepts
  2. Disks and file storages
  3. Creating scheduled snapshots

Creating scheduled disk snapshots

Written by
Yandex Cloud
Updated at February 12, 2025
  • Cron expressions
    • Possible field values
    • Special characters
    • Examples of cron expressions
    • Special expressions
  • Storing snapshots
  • Snapshot names
  • Schedule statuses

You can configure automatic disk snapshot creation based on a schedule.

In the schedule, you specify:

  • Disks for which the snapshots will be created. One schedule can include multiple disks, and one disk can be added to multiple schedules.
  • Frequency of snapshot creation by hour, day, week, or cron expression. All times are now UTC±00:00.
  • Snapshot retention settings.
  • Scheduled snapshot description and labels (you can only use the API to add them to the schedule settings).

Note

Scheduled snapshots may be created with a slight delay depending on the current Compute Cloud load.

Snapshots are created in the same folder as the schedule, even if the schedule has disks from other folders.

A single snapshot can only be created for one disk at a time. All other schedules for the disk in question are ignored until a snapshot for this disk is created.

You can create snapshots of network disks and drives, such as HDDs, SSDs, and non-replicated SSDs, as well as ultra high-speed network storages with three replicas (SSD).

For non-replicated SSDs and ultra high-speed network storages with three replicas (SSD), the snapshot time is not determined.

To create snapshots of local disks residing on dedicated hosts, use Yandex Cloud Backup. This service supports Ubuntu, CentOS, CentOS Stream, and Windows Server.

A quota, which can be increased, applies to the number of schedules per cloud. Fixed limits apply to the number of disks in a schedule and the number of schedules for a disk.

Schedules can be used free of charge. You only pay for storing the snapshots. For more information, see Compute Cloud pricing policy.

Cron expressionsCron expressions

You can specify a snapshot schedule using a cron expression consisting of five fields: Minutes Hours Day-of-month Month Day-of-week. You can also use special expressions, e.g., to create snapshots every hour or every day.

Possible field valuesPossible field values

Field
name
Acceptable
values
Supported
special
characters
Minutes 0–59 ,, -, *, /
Hours 0–23 (UTC+0) ,, -, *, /
Day of month 1–31 ,, -, *, ?, /
Month 1–12
JAN–DEC
,, -, *, /
Day of week 1–7
MON–SUN
,, -, *, ?, /

Note

The names of and days are case-insensitive, i.e., MON is the same as mon.

Special charactersSpecial characters

You can use the following special characters in cron expressions:

  • *: Select all values in the field.

    * character in the Hours field: Snapshots are created every hour.

  • ?: Select any field value. You cannot specify Day of month and Day of week at the same time. If you entered a value or * in one of these fields, enter ? in the other.

    10 in Day of month and ? in Day of week: Snapshots are created every tenth day of the month.

  • -: Select a range of values.

    The 10-12 range in Hours: Snapshots are created at 10 a.m., 11 a.m., and 12 p.m.

  • ,: Select multiple values.

    MON, WED, FRI in the Day of week field: Snapshots are created on Monday, Wednesday, and Friday.

  • /: Increment the value.

    2/6 in Hours: Snapshots are created at 2 a.m., 8 a.m., 2 p.m., and 8 p.m.

Examples of cron expressionsExamples of cron expressions

Cron expression Description
0 * ? * * Snapshots are created at the start of every hour.
15 10 ? * * Snapshots are created every day at 10:15 a.m.
0 9,18 ? * 1-5 Snapshots are created every weekday at 9 a.m. and 9 p.m.

Special expressionsSpecial expressions

Cron expression Description The same as
@hourly Snapshots are created at the start of every hour. 0 * ? * *
@daily
@midnight
Snapshots are created every day at midnight. 0 0 ? * *
@weekly Snapshots are created every Sunday at midnight. 0 0 * * SUN
@monthly Snapshots are created every first day of the month at midnight. 0 0 1 * *
@yearly
@annually
Snapshots are created every year on January 1 at midnight. 0 0 1 1 *

Storing snapshotsStoring snapshots

With schedules, you can set and configure a snapshot retention policy. For each disk included in a schedule, you can store:

  • All created scheduled snapshots.
  • Only the last few snapshots. The oldest snapshots created on schedule are automatically deleted once the specified number is exceeded. For example, if you want to keep only the last five snapshots, the first snapshot is deleted after the sixth one is created, the second is deleted after the seventh one is created, etc.
  • Only the snapshots younger than a certain age, e.g., those created during the last few days. The oldest snapshots created on schedule are automatically deleted once the specified age is reached.

The retention policy applies to all disks in a schedule.

Snapshots are deleted only while the schedule is active (its status is ACTIVE).

Snapshot namesSnapshot names

For a scheduled snapshot, a name up to 63 characters long is generated. The name consists of the following items separated with underscores:

  • Name of a virtual machine the disk is attached to (up to 24 characters) or the unattached line if the disk is not attached to any VM.
  • Disk name (up 20 characters).
  • Snapshot creation date and time (UTC) in YYYYMMDDhhmm format (year, month, day, hour, and minute).
  • Line consisting of four random alphanumeric characters.

For example, if test-disk-with-a-long-name is attached to test-vm, its scheduled snapshot created on September 1, 2022 at 03:30 p.m. UTC will have the following name:

test-vm_test-disk-with-a-lon_202209011530_pd2k

Schedule statusesSchedule statuses

  • CREATING: Schedule is being created.
  • ACTIVE: Schedule is active: it is used to create new disk snapshots and delete the old ones (if you selected the relevant option in the snapshot retention settings).
  • UPDATING: Schedule settings or the list of attached disks are being updated.
  • INACTIVE: Schedule has been paused, snapshots are not created or deleted.
  • DELETING: Schedule is being deleted.

All snapshot creation or deletion operations that started prior to changing, interrupting or deleting the schedule will be completed.

See alsoSee also

  • Guides on disk snapshots and schedules

Was the article helpful?

Previous
Disk snapshots
Next
Non-replicated disk placement groups
© 2025 Direct Cursus Technology L.L.C.