This post is a community service. I am testing VMC SDDC with NSX-T (all new ones are with NSX-T) and restored a bunch of VMs from our onprem Veeam.
During restore, the last page ask you to map networks. As I pre-created all the networks in NSX-T (actually VMC interface, but not relevant), I was surprised to find that in the network selection there are 0 networks shown. To those who are not familiar with VMC SDDC with NSX-T - this is the only network type you can use - called "opaque network".
Long story short, I opened a support ticket and was told by support Veeam currently does not support NSX-T and there is no ETA. Quote:
For those who need this - you are welcome to +1 the post, contact support, etc.Unfortunately, NSX-T is not supported with Veeam now - we're not able to see these networks, you can't also select them in replication jobs or surebackup jobs, for example. This is planned to be added in future releases, as far as I know, but there's no ETA that support team can provide on this.
Apparently, the network config of the VMs was OK - meaning as the network names were the same as in onprem, the NICs were configured with the correct networks. The only thing remained to resolve was the "StartConnected" property - easily fixed by a quick PowerCli script. The cause of this - if Veeam does not recognize the network object during restore, the NIC will be "disconnected", meaning the "StartConnected" property is deselected after restore.
Note that you must use the latest PowerCli or during "network name set" operation you will get an exception.