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 Cloud Backup
  • Getting started
    • All guides
    • Activating the service
      • Leasing a BareMetal server with a connection to Cloud Backup
      • Connecting an existing BareMetal server to Cloud Backup
      • Reconnecting a BareMetal server to Cloud Backup
      • Restoring a 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. Restoring a Cloud Backup agent

Restoring the Cloud Backup agent after a Linux kernel update

Written by
Yandex Cloud
Updated at April 1, 2025

Updating the Linux kernel on a VM or BareMetal server connected to Cloud Backup may affect the performance of the Cloud Backup agent: it will not be able to create a backup of the VM/server or recover the VM/server from a backup.

This may affect the agent’s performance, since the SnapAPI module (developed by the backup provider for the agent to work with disks and built by the DKMS framework for a specific Linux kernel) may not update after updating the kernel and may therefore cease to match the kernel version.

To restore the Cloud Backup agent’s performance affected by a Linux kernel update, you need to update the version of the Linux kernel headers DKMS refers to when building the SnapAPI module. Once the kernel header version matches the kernel version, DKMS will rebuild the SnapAPI module for the required Linux kernel version at the next start of the VM or BareMetal server.

Debian/Ubuntu
  1. Make sure the Linux kernel version does not match that of the kernel headers:

    • To find out the Linux kernel version, run this command in the terminal:

      uname -r
      

      Result:

      6.1.0-31-amd64
      
    • To find out the version of the Linux kernel headers, run this command:

      sudo apt list --installed | grep header
      

      Result:

      linux-headers-6.1.0-27-amd64/stable,now 6.1.115-1 amd64 [installed]
      linux-headers-6.1.0-27-common/stable,now 6.1.115-1 all [installed,automatic]
      

    As you can see from the command outputs, the versions are different: the Linux kernel version is 6.1.0-31, and the Linux kernel header version is 6.1.0-27.

  2. Install the linux-headers package for the new Linux kernel:

    sudo apt install linux-headers-$(uname -r)
    
  3. Make sure the new kernel headers have been added:

    sudo apt list --installed | grep header
    

    Result:

    linux-headers-6.1.0-27-amd64/stable,now 6.1.115-1 amd64 [installed]
    linux-headers-6.1.0-27-common/stable,now 6.1.115-1 all [installed,automatic]
    linux-headers-6.1.0-31-amd64/stable-security,now 6.1.128-1 amd64 [installed]
    linux-headers-6.1.0-31-common/stable-security,now 6.1.128-1 all [installed,automatic]
    
  4. Reboot your OS:

    sudo reboot
    

    During the reboot, the DKMS framework will rebuild the SnapAPI module for the required Linux kernel version and the Cloud Backup agent will start operating.

If you were unable to recover your Cloud Backup agent for any reason, contact support.

Was the article helpful?

Previous
Reconnecting a BareMetal server to Cloud Backup
Next
Creating a policy
Yandex project
© 2025 Yandex.Cloud LLC