Troubleshooting in Cloud Backup
This section describes typical problems you may encounter while using Cloud Backup and gives troubleshooting recommendations.
Why cannot I add a VM to Cloud Backup?
Make sure that:
- Cloud Backup supports the VM operating system.
- Service account linked to your VM has the
backup.editorrole assigned. - Security group is correctly configured for your VM.
For more information, see Connecting Compute Cloud VM instances to Cloud Backup.
How to reconnect to the service a VM deleted from Cloud Backup?
If you have deleted a VM from Cloud Backup and want to reconnect it to the service, use this guide:
How can I reconnect a VM to Cloud Backup after restoring its backup to another VM?
A virtual machine becomes outdated after restoring its backup to another VM. To avoid conflicts between the source and target VMs when making backups, refresh the connection of the outdated VM to Cloud Backup.
An error occurs when trying to restore a VM from a backup
Error message:
Not all of the items are mapped. Please, check your target instance and its volumes.
The error occurs because Cloud Backup cannot find a disk on the target VM that matches the size criterion.
The boot disk size of the target VM must be at least equal to that of the source VM.
Check the disks on the target VM and increase their size as needed. You can also use another VM with appropriate parameters.
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 your VM has the
backup.editorrole assigned. - 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.