Network Mapping Slowness Optimization

[zjerinasite]

We are using Powershell in order to do the network mapping for replication jobs.
The input for our script is source vCenter, target vCenter and the networks we want to do the mapping for.
As far as I understand the only way to do the mapping is:
- Get source and target vCenter
- Get the ESXi hosts for each vCenter
- Find the required networks by looping over the ESXi hosts
- Get the job with: Get-VBRJob
- Update network mapping using: Set-VBRViReplicaJob

This seems very counter intuitive and slow, because before using the script we already know which network IDs we want to map but we still have to fetch the networks every time we update the network mapping.

Is there any way to just construct the source and target networks, or to just pass network IDs to Set-VBRViReplicaJob SourceNetwork and TargetNetwork parameters?
Also is there any API or any other way of doing replication job management instead of using Powershell?

[oleg.feoktistov]

Hi,

Currently the only official automated way to manage network mapping for replication jobs is the one you mentioned above, and Set-VBRViReplicaJob accepts only full objects for SourceNetwork and TargetNetwork parameters.
We have plans to enhance our VBR REST API though adding replication jobs in one of our vNext releases, so it might be easier then in terms of steps quantity with just knowing networkId.

Thanks,
Oleg

[zjerinasite]

Thank you for your support, the feature would be very useful.