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
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for Valkey™
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Updating cluster settings
      • Valkey™ version upgrade
      • Stopping and starting a cluster
      • Managing cluster hosts
      • Migrating hosts to a different availability zone
      • Managing backups
      • Deleting a cluster
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Restoring clusters from backups
  • Creating a backup
  • Getting a list of backups
  • Getting information about backups
  • Setting the backup start time
  1. Step-by-step guides
  2. Clusters
  3. Managing backups

Managing backups in Yandex Managed Service for Valkey™

Written by
Yandex Cloud
Updated at May 13, 2025
  • Restoring clusters from backups
  • Creating a backup
  • Getting a list of backups
  • Getting information about backups
  • Setting the backup start time

You can create backups and restore clusters from existing backups.

Yandex Managed Service for Valkey™ also creates automatic daily backups. You can set the backup start time:

Restoring clusters from backups

When you restore a cluster from a backup, you create a new cluster with the backup data. If the folder has insufficient resources to create such a cluster, you will not be able to restore from the backup. The average backup recovery speed is 10 MBps.

If you chose the local-ssd disk type when restoring the cluster from a backup, add at least two hosts per shard.

Management console
CLI
REST API
gRPC API

To restore an existing cluster from a backup:

  1. In the management console, go to the folder to restore the cluster in.
  2. Select Yandex Managed Service for Valkey™.
  3. Click the cluster name and open the Backups tab.
  4. In the line of the appropriate backup, click and select Restore cluster.
  5. Set up the new cluster. You can select a folder for the new cluster from the Folder list.
  6. Click Restore cluster.

To restore a previously deleted cluster from a backup:

  1. In the management console, go to the folder to restore the cluster in.
  2. Select Yandex Managed Service for Valkey™.
  3. In the left-hand panel, select Backups.
  4. Find the backup you need using the backup creation time and cluster ID. The ID column contains IDs formatted as <cluster_ID>:<backup_ID>.
  5. In the line of the appropriate backup, click and select Restore cluster.
  6. Set up the new cluster. You can select a folder for the new cluster from the Folder list.
  7. Click Restore cluster.

Yandex Managed Service for Valkey™ will launch the operation to create a cluster from the backup.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To restore a cluster from a backup:

  1. View a description of the CLI restore Valkey™ cluster command:

    yc managed-redis cluster restore --help
    
  2. Getting a list of available Valkey™ cluster backups:

    yc managed-redis backup list
    

    Result:

    +--------------------------+---------------------+----------------------+---------------------+
    |            ID            |     CREATED AT      |  SOURCE CLUSTER ID   |     STARTED AT      |
    +--------------------------+---------------------+----------------------+---------------------+
    | c9qlk4v13uq7********:... | 2020-08-10 12:00:00 | c9qlk4v13uq7******** | 2020-08-10 11:55:17 |
    | ...                                                                                         |
    +--------------------------+---------------------+----------------------+---------------------+
    
  3. Request creating a cluster from a backup:

    yc managed-redis cluster restore \
       --backup-id c9q287aqv5rf********:20181113T133617 \
       --name mynewrd \
       --environment=PRODUCTION \
       --network-name default \
       --host zone-id=ru-central1-a,subnet-id=b0rcctk2rvtr********,assign-public-ip=true,replica-priority=50 \
       --password P@ssWord \
       --disk-size 20
    

    This results in a new Valkey™ cluster with the following characteristics:

    • Name: mynewrd
    • Environment: PRODUCTION
    • Network: default
    • Host class: hm1.nano (one host); subnet: b0rcctk2rvtr********; availability zone: ru-central1-a; access: public; replica priority: 50.
    • Password: P@ssWord.
    • Network SSD storage (network-ssd): 20 GB

    The password must be between 8 and 128 characters long. The password must meet the [a-zA-Z0-9@=+?*.,!&#$^<>_-]* regular expression.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Use the Cluster.Restore method and make a request, e.g., via cURL:

    curl \
        --request POST \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --header "Content-Type: application/json" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters:restore' \
        --data '{
                  "backupId": "<backup_ID>",
                  "name": "<cluster_name>",
                  "environment": "<environment>",
                  "configSpec": {
                    "redis": {
                      "password": "<user_password>"
                    }
                  },
                  "hostSpecs": [
                    {
                      "zoneId": "<availability_zone>",
                      "subnetId": "<subnet_ID>",
                      "replicaPriority": "<host_priority>",
                      "assignPublicIp": <public_access_to_cluster_host>
                    },
                    { <similar_configuration_for_host_2> },
                    { ... },
                    { <similar_configuration_for_host_N> }
                  ],
                  "networkId": "<network_ID>",
                  "tlsEnabled": <encrypted_TLS_connection_support>
                }'
    

    Where:

    • backupId: Backup ID. To find out the ID, get a list of folder backups.

    • name: Cluster name.

    • environment: Environment, PRESTABLE or PRODUCTION.

    • configSpec.redis.password: User password.

    • hostSpecs: Host parameters:

      • zoneId: Availability zone.
      • subnetId: Subnet ID. Specify if two or more subnets are created in the selected availability zone.
      • replicaPriority: Priority for assigning the host as a master if the primary master fails.
      • assignPublicIp: Internet access to the host via a public IP address, true or false. You can enable public access only if the tlsEnabled parameter is set to true.
    • networkId: ID of the network the cluster will be in.

    • tlsEnabled: Support for encrypted TLS connections to the cluster, true or false.

      Warning

      You can only enable connection encryption when creating a new cluster. You cannot disable encryption for a cluster that it is enabled for.

  3. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the Cluster.Restore call and make a request, e.g., via gRPCurl:

    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "backup_id": "<backup_ID>",
              "name": "<cluster_name>",
              "environment": "<environment>",
              "config_spec": {
                "redis": {
                  "password": "<user_password>"
                }
              },
              "host_specs": [
                {
                  "zone_id": "<availability_zone>",
                  "subnet_id": "<subnet_ID>",
                  "replica_priority": "<host_priority>",
                  "assign_public_ip": <public_access_to_cluster_host>
                },
                { <similar_configuration_for_host_2> },
                { ... },
                { <similar_configuration_for_host_N> }
              ],
              "network_id": "<network_ID>",
              "tls_enabled": <encrypted_TLS_connection_support>
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.redis.v1.ClusterService.Restore
    

    Where:

    • backup_id: Backup ID. To find out the ID, get a list of folder backups.

    • name: Cluster name.

    • environment: Environment, PRESTABLE or PRODUCTION.

    • config_spec.redis.password: User password.

    • host_specs: Host parameters:

      • zone_id: Availability zone.
      • subnet_id: Subnet ID. Specify if two or more subnets are created in the selected availability zone.
      • replica_priority: Priority for assigning the host as a master if the primary master fails.
      • assign_public_ip: Internet access to the host via a public IP address, true or false. You can enable public access only if the tlsEnabled parameter is set to true.
    • network_id: ID of the network the cluster will be in.

    • tls_enabled: Support for encrypted TLS connections to the cluster, true or false.

      Warning

      You can only enable connection encryption when creating a new cluster. You cannot disable encryption for a cluster that it is enabled for.

  4. View the server response to make sure the request was successful.

Creating a backup

Management console
CLI
REST API
gRPC API
  1. In the management console, go to the folder to create a backup in.
  2. Select Yandex Managed Service for Valkey™.
  3. Click the cluster name and open the Backups tab.
  4. Click Create backup.

The service will start creating a backup without an additional confirmation.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To create a cluster backup:

  1. View a description of the CLI create Valkey™ backup command:

    yc managed-redis cluster backup --help
    
  2. Request the creation of a backup specifying the cluster name or ID:

    yc managed-redis cluster backup my-rd-cluster
    

    The cluster name and ID can be retrieved with the list of clusters.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Use the Cluster.Backup method and send the following request, e.g., via cURL:

    curl \
        --request POST \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>:backup'
    

    You can request the cluster ID with the list of clusters in the folder.

  3. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.Backup call and send the following request, e.g., via gRPCurl:

    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "cluster_id": "<cluster_ID>"
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.redis.v1.ClusterService.Backup
    

    You can request the cluster ID with the list of clusters in the folder.

  4. View the server response to make sure the request was successful.

Warning

While you are creating your backup, the cluster performance might degrade.

Getting a list of backups

Management console
CLI
REST API
gRPC API

To get a list of cluster backups:

  1. In the management console, go to the relevant folder.
  2. Select Yandex Managed Service for Valkey™.
  3. Click the cluster name and open the Backups tab.

To get a list of all backups in a folder:

  1. In the management console, go to the relevant folder.
  2. Select Yandex Managed Service for Valkey™.
  3. In the left-hand panel, select Backups.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To get a list of Valkey™ cluster backups available in the default folder, run the command:

yc managed-redis backup list

Result:

+--------------------------+---------------------+----------------------+---------------------+
|            ID            |     CREATED AT      |  SOURCE CLUSTER ID   |     STARTED AT      |
+--------------------------+---------------------+----------------------+---------------------+
| c9qlk4v13uq7********:... | 2020-08-10 12:00:00 | c9qlk4v13uq7******** | 2020-08-10 11:55:17 |
| c9qpm90p3pcg********:... | 2020-08-09 22:01:04 | c9qpm90p3pcg******** | 2020-08-09 21:30:00 |
+--------------------------+---------------------+----------------------+---------------------+
  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. To get a list of cluster backups:

    1. Use the Cluster.ListBackups method and send the following request, e.g., via cURL:

      curl \
          --request GET \
          --header "Authorization: Bearer $IAM_TOKEN" \
          --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>/backups'
      

      You can request the cluster ID with the list of clusters in the folder.

    2. View the server response to make sure the request was successful.

  3. To get a list of backups for all the clusters in a folder:

    1. Use the Backup.List method and send the following request, e.g., via cURL:

      curl \
          --request GET \
          --header "Authorization: Bearer $IAM_TOKEN" \
          --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/backups' \
          --url-query folderId=<folder_ID>
      

      You can request the folder ID with the list of folders in the cloud.

    2. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. To get a list of cluster backups:

    1. Use the ClusterService.ListBackups call and send the following request, e.g., via gRPCurl:

      grpcurl \
          -format json \
          -import-path ~/cloudapi/ \
          -import-path ~/cloudapi/third_party/googleapis/ \
          -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \
          -rpc-header "Authorization: Bearer $IAM_TOKEN" \
          -d '{
                "cluster_id": "<cluster_ID>"
              }' \
          mdb.api.cloud.yandex.net:443 \
          yandex.cloud.mdb.redis.v1.ClusterService.ListBackups
      

      You can request the cluster ID with the list of clusters in the folder.

    2. View the server response to make sure the request was successful.

  4. To get a list of backups for all the clusters in a folder:

    1. Use the BackupService.List call and send the following request, e.g., via gRPCurl:

      grpcurl \
          -format json \
          -import-path ~/cloudapi/ \
          -import-path ~/cloudapi/third_party/googleapis/ \
          -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/backup_service.proto \
          -rpc-header "Authorization: Bearer $IAM_TOKEN" \
          -d '{
                "folder_id": "<folder_ID>"
              }' \
          mdb.api.cloud.yandex.net:443 \
          yandex.cloud.mdb.redis.v1.BackupService.List
      

      You can request the folder ID with the list of folders in the cloud.

    2. View the server response to make sure the request was successful.

Getting information about backups

Management console
CLI
REST API
gRPC API

To get information about the backup of an existing cluster:

  1. In the management console, go to the folder with the cluster to get backup information for.
  2. Select Yandex Managed Service for Valkey™.
  3. Click the cluster name and open the Backups tab.

To get information about the backup of a previously deleted cluster:

  1. In the management console, go to the folder the deleted cluster was in.
  2. Select Yandex Managed Service for Valkey™.
  3. In the left-hand panel, select Backups.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To get information about a Valkey™ cluster backup, run the command:

yc managed-redis backup get <backup_ID>

You can retrieve the backup ID with the list of backups.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Use the Backup.Get method and send the following request, e.g., via cURL:

    curl \
        --request GET \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/backups/<backup_ID>'
    

    You can request the backup ID together with the list of backups.

  3. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the BackupService.Get call and send the following request, e.g., via gRPCurl:

    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/backup_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "backup_id": "<backup_ID>"
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.redis.v1.BackupService.Get
    

    You can request the backup ID together with the list of backups.

  4. View the server response to make sure the request was successful.

Setting the backup start time

Management console
CLI
REST API
gRPC API

When creating or updating a cluster, you can set the backup start time under Advanced settings.

To set the backup start time, use the --backup-window-start flag. Time is given in HH:MM:SS format.

yc managed-redis cluster create \
  --name <cluster_name> \
  --environment <environment> \
  --network-name <network_name> \
  --host zone-id=<availability_zone>,subnet-id=<subnet_ID> \
  --backup-window-start 10:25:00

Where --environment is the environment: prestable or production.

To change the backup start time in an existing cluster, use the update command:

yc managed-redis cluster update \
   --name <cluster_name> \
   --backup-window-start 11:25:00
  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Use the Cluster.Update method and send the following request, e.g., via cURL:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

    curl \
        --request PATCH \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --header "Content-Type: application/json" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>' \
        --data '{
                  "updateMask": "configSpec.backupWindowStart",
                  "configSpec": {
                    "backupWindowStart": {
                      "hours": "<hours>",
                      "minutes": "<minutes>",
                      "seconds": "<seconds>",
                      "nanos": "<nanoseconds>"
                    }
                  }
                }'
    

    Where:

    • updateMask: List of parameters to update as a single string, separated by commas.

      In this case, only one parameter is provided.

    • configSpec.backupWindowStart: Backup window settings.

      In this parameter, specify the backup start time:

      • hours: Between 0 and 23 hours.
      • minutes: Between 0 and 59 minutes.
      • seconds: Between 0 and 59 seconds.
      • nanos: Between 0 and 999999999 nanoseconds.

    You can request the cluster ID with the list of clusters in the folder.

  3. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the update_mask parameter as an array of paths[] strings.

    Format for listing settings
    "update_mask": {
        "paths": [
            "<setting_1>",
            "<setting_2>",
            ...
            "<setting_N>"
        ]
    }
    
    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "cluster_id": "<cluster_ID>",
              "update_mask": {
                "paths": [ "config_spec.backup_window_start" ]
              },
              "config_spec": {
                "backup_window_start": {
                  "hours": "<hours>",
                  "minutes": "<minutes>",
                  "seconds": "<seconds>",
                  "nanos": "<nanoseconds>"
                }
              } 
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.redis.v1.ClusterService.Update
    

    Where:

    • update_mask: List of parameters to update as an array of paths[] strings.

      Only one parameter is provided in this case.

    • config_spec.backup_window_start: Backup window settings.

      In this parameter, specify the backup start time:

      • hours: Between 0 and 23 hours.
      • minutes: Between 0 and 59 minutes.
      • seconds: Between 0 and 59 seconds.
      • nanos: Between 0 and 999999999 nanoseconds.

    You can request the cluster ID with the list of clusters in the folder.

  4. View the server response to make sure the request was successful.

Was the article helpful?

Previous
Migrating hosts to a different availability zone
Next
Deleting a cluster
Yandex project
© 2025 Yandex.Cloud LLC