Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Backup
    • All guides
    • Activating the service
      • Leasing a BareMetal server connected to Cloud Backup
      • Connecting an existing BareMetal server to Cloud Backup
      • Reconnecting a BareMetal server to Cloud Backup
      • Restoring the Cloud Backup agent
    • Viewing service resource operations
    • Limiting RAM usage by the Cloud Backup agent
    • Viewing backup statistics
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Step-by-step guides
  2. BareMetal in Cloud Backup
  3. Reconnecting a BareMetal server to Cloud Backup

Reconnecting a Yandex BareMetal server to Cloud Backup

Written by
Yandex Cloud
Updated at July 9, 2025

If you deploy a backup of one server to another, the original server's connection to Cloud Backup becomes outdated. To continue backing up the original server and avoid conflicts with the new one, upgrade the source server connection to Cloud Backup:

  1. To connect a BareMetal server to Cloud Backup, you need a service account with at least the backup.editor and baremetal.editor roles. Create one or assign the required roles to an existing service account.

  2. Get an IAM token.

  3. Reconnect to Cloud Backup from the outdated server:

    Linux
    1. Connect to the server over SSH.

    2. On your server, install curl, wget, gawk, uuid-dev, and uuidgen.

      Note

      If you are using a distribution other than Ubuntu, install the specified tools using your package manager.

      sudo apt install curl
      sudo apt install wget
      sudo apt install gawk
      sudo apt install uuid-dev
      sudo apt install uuid-runtime
      
    3. Update your connection to Cloud Backup:

      wget https://storage.yandexcloud.net/backup-distributions/agent_reinit_bms.sh
      sudo bash agent_reinit_bms.sh -t=<IAM_token>
      

      Where -t is the IAM token you got earlier.

      Result:

      ...
      Deleting old resource bound for instance_id epdoe4g6dbq4******** and resource_id: F07543A1-BDC1-415A-A143-C18E********
      Updating ids in Cloud Backup
      Finished
      
  4. Make sure the server is connected to Cloud Backup:

    CLI

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

    By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

    Get a list of BareMetal servers connected to Cloud Backup:

    yc backup resource list --type bms
    

    Where --type is the resource type.

    Result:

    compute_instance_id: epd5sk4auijm********
    created_at: "2024-11-17T10:29:40.436155166Z"
    updated_at: "2024-11-17T10:32:54.580592713Z"
    online: true
    enabled: true
    status: IDLE
    next_backup_time: "2024-11-24T00:00:00Z"
    resource_id: ad216376-a8d7-4c28-9a8d-b4ad********
    is_active: true
    init_status: REGISTRED
    metadata: "null"
    type: BMS
    
  5. Link the server to a backup policy.

Was the article helpful?

Previous
Connecting an existing BareMetal server to Cloud Backup
Next
Restoring the Cloud Backup agent
© 2025 Direct Cursus Technology L.L.C.