Repository navigation
Failed to create a new instance from backup with Veeam using vSAN storage #11888
Description
Discussed in #11886
Originally posted by leolns October 21, 2025
problem
Cloudstack 4.21.0.0 + VMware 8u3g + vSAN + Veeam 12 environment.
When trying to create a new instance from an existing backup, an error occurs because the datastore cannot be found. The datastore lookup is using the CloudStack UUID instead of the volume name.
$ds = Find-VBRViDatastore -Server:$server -Name "0f2b59684453331eb366a6d7036bae96"
Find-VBRViDatastore doesnt accept uuid, it needs vmware volume name
ERROR [c.c.u.s.SshHelper] (API-Job-Executor-120:[ctx-e94e8dfc, job-58501, ctx-8df14098]) (logid:d58f3113) SSH execution of command PowerShell Import-Module Veeam.Backup.PowerShell -WarningAction SilentlyContinue;$ProgressPreference='SilentlyContinue';$points = Get-VBRRestorePoint;foreach($point in $points) { if ($point.Id -eq '4bf0faea-53e5-4d3f-bf2c-8f83a2104e7d') { $restorePoint = $point; break; } };$server = Get-VBRServer -Name "10.10.10.103";$ds = Find-VBRViDatastore -Server:$server -Name "0f2b59684453331eb366a6d7036bae96";$job = Start-VBRRestoreVM -RestorePoint:$restorePoint -Server:$server -Datastore:$ds -VMName "i-8-662-TESTEDEMOBKPRESTORE" -RunAsync;while (-not (Get-VBRRestoreSession -Id $job.Id).IsCompleted) { Start-Sleep -Seconds 10 } has an error status code in return. Result output: Find-VBRViDatastore : Cannot convert 'System.Object[]' to the type 'Veeam.Backup.Core.Common.CHost' required by ^M
parameter 'Server'. Specified method is not supported.^M
At line:1 char:342^M
+ ... -Name 10.254.254.10;$ds = Find-VBRViDatastore -Server:$server -Name 0 ...^M
+ ~~~~~~~^M
+ CategoryInfo : InvalidArgument: (:) [Find-VBRViDatastore], ParameterBindingException^M
+ FullyQualifiedErrorId : CannotConvertArgument,Veeam.Backup.PowerShell.Cmdlets.FindVBRViDatastore^M
^M
Start-VBRRestoreVM : Cannot convert 'System.Object[]' to the type 'Veeam.Backup.Core.Common.CHost' required by ^M
parameter 'Server'. Specified method is not supported.^M
At line:1 char:451^M
versions
Cloudstack 4.21.0.0 + VMware 8u3g + vSAN + Veeam 12
The steps to reproduce the bug
Try to create a new instance from backup
What to do about it?
Find-VBRViDatastore doesnt accept uuid, it needs vmware volume name
Activity
abh1sar commentedon Oct 22, 2025
Yes, this is a bug in cloudstack.
For NFS storage, the datastore name in vmware is created from the primary_storage uuid in cloudstack by removing all hyphens.
VMFS (VSan) keeps the native datastore name. (CloudStack sets a custom field cloud.uuid equal to the primary_storage uuid for reference)
The Create new Instance from backup code is deriving the datastore name from primary_storage uuid, which works for NFS storage but not for VMFS.
The same issue is present in Restore single volume from veeam in all versions, as Create new instance feature has derived the code from the Restore single Volume feature.
github-actions commentedon Jul 1, 2026
🎯 Triage report
When creating a new instance from a Veeam backup in a VMware/vSAN environment, the CloudStack PowerShell script passes the primary storage UUID (without hyphens, NFS-style) to
Find-VBRViDatastore, but vSAN datastores have a native datastore name that is different from the CloudStack UUID. This causesFind-VBRViDatastoreto fail, and the restore is aborted. The same bug also affects the "Restore single volume from Veeam" path.📊 Assessment
🔗 Similar issues
💡 Notes and suggestions
cloud.uuidcustom attribute on the datastore but the actual datastore name is the native VMware name.cloud.uuidcustom field lookup on the vCenter datastore list) instead of the UUID.datastoreNamefield to the primary storage metadata that is populated with the correct native name at pool registration time.Add this agentic workflows to your repo
To install this agentic workflow, run