| KB ID: | 4065 |
| Product: | Veeam Backup for Google Cloud Platform 1.0 |
Challenge
Veeam Backup for GCP fails to restore a disk of a VM instance.
The issue is most likely to occur when restoring to the original location, while the source disk still exists there.
Veeam Backup for Google Cloud Platform 2.0 Behavior Change
The error is replaced by a warning in the Veeam Backup for Google Cloud Platform 2.0, and the workflow is different. In Veeam Backup for Google Cloud Platform 2.0, if there is a disk conflict, restore to the original location will be disabled. If a disk restore is performed to the same region and zone as the original one, a suffix will be automatically assigned to the disk name to avoid collisions.
Solution
Due to technical limitations in Google Compute Engine, disks cannot have the same name. Additionally, disks cannot be renamed.
To work around the issue, try one of the following solutions:
- Manually specify a new name for the disk in the Disk Restore wizard.
- Do not specify a new name in the Disk Restore wizard — Veeam Backup for GCP will automatically append an autogenerated suffix to the name of the restored disk.
- Delete the source disk before proceeding with the restore. However, this is not recommended as any problems with the restore could result in lost data.