Troubleshooting in Cloud Backup
This section describes typical problems you may encounter while using Cloud Backup and gives troubleshooting recommendations.
BareMetal is at the Preview stage.
-
Why cannot I add a VM or Yandex BareMetal server to Cloud Backup?
-
How do I reconnect a VM or BareMetal server deleted from Cloud Backup?
-
Error when trying to recover a VM or BareMetal server from a backup
Why cannot I add a VM or Yandex BareMetal server to Cloud Backup?
Make sure that:
- The VM is created from a supported image or (if the Cloud Backup agent is installed manually) Cloud Backup supports the VM's operating system.
- Service account linked to the VM has the
backup.editorrole. - Security group is correctly configured for the VM.
For more information, see Connecting Compute Cloud VM instances to Cloud Backup.
- The server runs a supported operating system.
- The service account whose IAM token is used to install the Cloud Backup agent has the
backup.editorrole. - The server has a public IP address assigned.
For more information, see Connecting a BareMetal server to Cloud Backup.
How do I reconnect a VM or BareMetal server deleted from Cloud Backup?
If you have deleted a VM or BareMetal server from Cloud Backup and want to reconnect it to the service, follow this guide:
- Reinstall the Cloud Backup agent according to this guide.
How do I reconnect a VM or BareMetal server to Cloud Backup after restoring its backup to another VM or server?
A virtual machine becomes outdated after its backup is restored to another VM. To avoid conflicts between the source and target VMs when performing a backup, refresh the outdated VM's connection to Cloud Backup.
A BareMetal server becomes outdated after its backup is restored to another server. To avoid conflicts between the original and target BareMetal servers when performing a backup, refresh the outdated server's connection to Cloud Backup.
I get an error when trying to restore a VM or BareMetal server from a backup
Error message:
Not all of the items are mapped. Please, check your goal instance and its volumes.
The error occurs because Cloud Backup cannot find a suitably sized disk on the target VM.
The boot disk of the target VM or BareMetal server must be at least the size of that of the source VM.
Check the target VM disks and increase their size as needed. You can also use another VM or BareMetal server with suitable parameters.
Note
To avoid errors when recovering from a backup, start by comparing the parameters of the disks and partitions of the backup against those of the VM or Yandex BareMetal server. For more information, see Viewing the parameters of backup disks and partitions.
Error when connecting to a Windows VM
Error message:
Fetching agent id from config
Iteration 0: The term 'acropsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Make sure that:
- Cloud Backup supports the VM operating system.
- Service account linked to the VM has the
backup.editorrole. - Network access for your VM is enabled.
- The PowerShell execution policies allow scripts. If they do not, allow scripts and restart PowerShell. For more information, see the Microsoft documentation.
How do I update the Cloud Backup agent on a VM?
See this guide: Updating the Cloud Backup agent on a VM.
Why are backups no longer created after the OS update?
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.
To update Linux kernel header versions, follow these tutorials: Restoring the Cloud Backup agent on a VM and Restoring the Cloud Backup agent on a BareMetal server.
Creating incremental backups of a VM or BareMetal server is taking longer than usual
Antivirus activity may affect the time required to create incremental backups under a policy with the fast backup option enabled (fastBackupEnabled). For more information, see Interaction with an antivirus.