@Anand K , it could be the credentials used to reach the vms, though we should check the logs first.

Can you see what JobManager.log and vsbkp.log show for this Job ID and paste it here?  Remove any identifiable information if you wish.

@Mike Struening,

If the proxy of Virtual machine, the VM backup job is working fine. But the proxy of physical server it's getting an error.

@Anand K , are you saying the actual physical server is failing?  Can you find the first line in JobManager.log for this job so I can see the iDA details?

@Mike Struening,

If the VSA proxy will use in physical server, the backup job is getting failure.

For Fusioncompute environment, the commvault proxy recommentation as mentioned in below:

The Virtual Server Agent can be installed on one or more machines, so that those machines can serve as VSA proxies. A VSA proxy manages backup and restore operations for guest VMs in your environment, eliminating the need to install agents on guest VMs.

The Virtual Server Agent (VSA) must be installed on a physical or virtual machine running supported versions of Linux or Windows. You must add at least one Virtual Server Agent (VSA) proxy for the FusionCompute Virtual Resource Manager (VRM). Additional proxies can be added as needed.

You can install the MediaAgent on the same machine as the CommServe system or on a separate machine.

Ok, so you’re saying you have multiple MA proxies, but if the job uses a physical MA (instead of one of your virtual MAs) the job fails?

Can you see what JobManager.log and vsbkp.log show for this Job ID and paste it here?  Remove any identifiable information if you wish.

@Anand K , were you able to resolve this issue on your own?  If so, can you share how?

If not, share the log excerpts mentioned above.

Thanks!

From Anand:

We have configured Virtual proxy using LAN based backup of VM's.