Connecting Yandex BareMetal servers to Cloud Backup

To back up your BareMetal servers in Cloud Backup, you need them connected to the service and properly set up.

For more on connecting BareMetal servers to Cloud Backup, see Managing BareMetal servers in Cloud Backup.

For the Cloud Backup connection to work correctly, link to the server a service account with the baremetal.editor and backup.user roles or higher and configure network access.

After you connect it to Cloud Backup, link the BareMetal server to a backup policy.

You can also link a policy to a BareMetal server when ordering the latter. A policy is linked asynchronously after you create and initialize a server and after you install and configure the Cloud Backup agent. This may take up to 10-15 minutes.

Supported Cloud Marketplace images with automatic installation of the Cloud Backup agentSupported Cloud Marketplace images with automatic installation of the Cloud Backup agent

On BareMetal servers, the Cloud Backup agent is available for automatic installation if ordering servers using the following Cloud Marketplace images:

• CentOS 7
• Debian 11
• Ubuntu 18.04 LTS
• Ubuntu 20.04 LTS
• Ubuntu 22.04 LTS
• Ubuntu 24.04 LTS

Unaided installation on a supported operating systemUnaided installation on a supported operating system

You can install the Cloud Backup agent manually on a BareMetal server running one of these operating systems:

• CentOS 7.
• Debian 11.
• Ubuntu 16.04 LTS.
• Ubuntu 18.04 LTS.
• Ubuntu 20.04 LTS.
• Ubuntu 22.04 LTS.
• Ubuntu 24.04 LTS.

To install the agent on a server, follow this guide on connecting a BareMetal server to Cloud Backup.

If you have issues installing the Cloud Backup agent, contact support.

Updating the operating system kernelUpdating the operating system kernel

Updating the Linux kernel on a resource connected to Cloud Backup may affect the performance of the Cloud Backup agent: it will not be able to create a backup of the resource or recover it 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 resource.

To upgrade the Linux kernel header version, follow this guide on restoring the Cloud Backup agent on a BareMetal server.

Service accountService account

A service account is a special account the Cloud Backup agent uses to get registered with the Cyberprotect provider.

When renting a BareMetal server you want to configure backups for in Cloud Backup, you need to link to it a service account with the baremetal.editor and backup.user roles or higher.

You can assign the role to an existing service account or create a new service account with required roles.

Network access permissionsNetwork access permissions

For the Cloud Backup agent to be able to exchange data with the backup provider servers, make sure the BareMetal server has network access to the IP addresses of the Cloud Backup resources as per the table below:

To provide network access:

• When renting a server, select From ephemeral subnet or From a dedicated subnet in the Public address field to assign a public IP address to the server.
• Make sure the sever network settings do not block outgoing traffic to the resources specified above.

Connection statusesConnection statuses

You can view the server connection to Cloud Backup status info in the management console on the server list page in BareMetal. The following statuses are available:

• Connected: Cloud Backup is connected to the server, backups are being created as per the specified policies, the Cloud Backup agent is online.
• No backup policy: Cloud Backup is connected, but there are no associated policies; no backups are being created.
• Failed: Agent is offline, or agent registration failed.
• Not connected: Cloud Backup is not connected to the server.

See alsoSee also

• Managing BareMetal servers in Cloud Backup
• Connecting Yandex Compute Cloud VMs to Cloud Backup
• Connecting VMs and servers from outside Yandex Cloud to Cloud Backup