Hi @Maximiliano.J 

If you get a discovery error then it could likely be communications or permissions here.

Can you share the error you get please?

You can check the CVD.log of the destination VSA proxy to see if there are any liked errors reported.

If this is a priority for you, I would suggest raising a support case to get this resolved more quickly.

Best Regards,

Michael

hello. do you need a vsa in vmware for this task? because we don't have a vsa for backups in vmware. we do them by integration and with a physical MA.

we have the following on-premise infrastructure
commserv -->windows
2 x Linux physical MA
Storage Data Doming

And in the cloud VSA Ami installed from commvault's markplace for aws-
And full backup in the cloud
I do not see connection between the VSA of the nuve and the esxi hosts or the vcenter to ports 443 and 902-

It sounds like it is using the wrong infrastructure machine to access vCenter - perhaps is trying to use the cloud VSA AMI you deployed which will unlikely to have access to vCenter over the internet.

Try overriding the restore Media Agent from this option and choose your on-prem physical MA.

VSA is just a software package you can install anywhere to perform backups. You can install it on the physical Media Agent for sure. That will support NBD (over the network) based backups, or SAN if available. You can install the VSA on a virtual machine in the VMware environment for HotAdd style backups, but the way you have it now is OK.