[Feature Request] Support per-disk datastore mapping for Start-VBRRestoreVM

[matsusan]

[Current Behavior]
When performing a full VM restore using PowerShell (Start-VBRRestoreVM) for a virtual machine that has multiple virtual disks, it is only possible to specify a single target datastore.
All virtual disks are restored to the same datastore.

In contrast, the GUI restore wizard already allows mapping individual virtual disks to different datastores during a full VM restore.

[Problem / Impact]
Customers need to migrate a large number of virtual machines to a different VMware environment using automation.
In many cases, the target environment requires placing different virtual disks (for example, OS disk and data disks) on different datastores.

Because Start-VBRRestoreVM does not provide an option to specify different datastores per virtual disk, this migration cannot be fully automated.
As a result, customers must perform restores manually via the GUI, which leads to significant operational overhead.

[Request]
Add a PowerShell option to Start-VBRRestoreVM that allows specifying datastore mapping per virtual disk, for example:
- Ability to pass a list or map of virtual disks and their target datastores
- Behavior consistent with the datastore selection capabilities already available in the GUI full VM restore wizard

Best regards,
Matsuyama

[david.domask]

Hi Matsuyama,

Understood on the limitation at this time; we do want to expand all the cmdlets to match options available in the Remote / Web Console and are working towards better coverage.

Consider using REST API for this as you have the ability to create disk mappings with the calls here.