Linking a resource to a backup policy

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. See the description of the CLI command for linking a BareMetal resource to a backup policy:

   yc backup policy apply --help
   

2. Get the ID of the backup policy you want to link a resource to:

   yc backup policy list
   

   Result:

   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   |          ID          |      FOLDER ID       |  NAME   | ENABLED |     CREATED AT      |     UPDATED AT      |
   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   | abc7n3wln123******** | ghi681qpe789******** | policy1 | true    | 2023-07-03 09:12:02 | 2023-07-03 09:12:43 |
   | deflqbiwc456******** | ghi681qpe789******** | policy2 | true    | 2023-07-07 14:58:23 | 2023-07-07 14:58:23 |
   +----------------------+----------------------+---------+---------+---------------------+---------------------+
   

3. Get the ID of the resource you want to link:

   yc backup vm list
   

   Result:

   +----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+
   |     INSTANCE ID      |             RESOURCE ID              | ONLINE | ENABLED | STATUS | STATUS PROGRESS | STATUS DETAILS |  LAST BACKUP TIME   |  NEXT BACKUP TIME   | ACTIVE |     CREATED AT      |     UPDATED AT      |    TYPE     |
   +----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+
   | ly5mzirn6xhd******** | 4fc0d855-b76c-****-99a4-bf01******** | true   | true    | IDLE   |               0 |                |                     |                     | true   | 2026-04-29 05:45:34 | 2026-04-29 05:54:21 | BMS         |
   | epd930eo5156******** | 6c58577d-409d-****-bc10-f464******** | true   | true    | IDLE   |               0 |                |                     |                     | true   | 2026-04-29 08:46:47 | 2026-04-29 08:54:00 | COMPUTE     |
   | cdgd246kiae3******** | d1fdd342-0ea8-****-9906-fa6c******** | false  | true    | IDLE   |               0 |                | 2026-04-27 13:07:05 | 2026-04-27 13:07:05 | true   | 2026-04-24 14:23:06 | 2026-04-29 08:54:33 | EXTERNAL_VM |
   +----------------------+--------------------------------------+--------+---------+--------+-----------------+----------------+---------------------+---------------------+--------+---------------------+---------------------+-------------+
   

4. Link the resource to the backup policy by specifying its ID:

   yc backup policy apply <policy_ID> \
     --instance-ids <resource_IDs>
   

   Where --instance-ids are the IDs of the Compute Cloud VMs, BareMetal servers, or external resources connected to Cloud Backup which you need to link to the backup policy. Multiple IDs should be comma-separated.

For more information about this command, see the CLI reference.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

To link a resource to a backup policy:

1. Describe the resource's link settings in the Terraform configuration file:

   resource "yandex_backup_policy_bindings" "test_backup_binding" {
     instance_id = "<resource_ID>"
     policy_id   = "<policy_ID>"
   }
   

   Where:

   • instance_id: ID of the resource you want to link to a backup policy.

     You can get the list of IDs of resources linked to Cloud Backup in the default folder by using the yc backup vm list Yandex Cloud CLI command.

   • policy_id: ID of the backup policy you want to link the resource to.

   For more on the properties of the yandex_backup_policy_bindings resource, see this provider guide.

2. Create the resources:

   1. In the terminal, navigate to the configuration file directory.

   2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      

   3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

   4. Apply the configuration changes:

      terraform apply
      

   5. Type yes and press Enter to confirm the changes.

   Terraform will create all the required resources. You can check the new resources using the management console or this CLI command:

    yc backup policy list-applications
   

Use the apply REST API method for the Policy resource or the PolicyService/Apply gRPC API call.