Error 91:32 When Trying to Restore a VM

It would be good to know if this was an FC, iSCSI or NFS datastore - my guess is FC - and if so, if you have multiple adapters or WWNs, commvault could be trying to associate the snap with the wrong adapter. You can override it using this setting: https://documentation.commvault.com/additionalsetting/details?name=sPortInfo

That is a common scenario, but just a guess for now ;)

Hi @tsmtmiller 

The “Unable to communicate...” error may be a physical issue with a network firewall blocking traffic on Commvault communications ports, usually 8400-8403, or may be an issue with Network Routes configured on the client(s) or client groups.

Please check if the restore target client is able to reach the MA [CVMA01] on communications ports, you can use  cvping to test connections using specific ports:
 

cvping 191.168.1.100 -Port 8403

Full usage details for CvPing (Windows):

USAGE: <Addr> [Family] [-BindIP <IP>] [-Port #] [-n #] [-t] [-i #]
 Addr   - Interface name or IP address
 Family - Family type. Values are -UseIPv4, -UseIPv6 or -UseIPAny. Default is -UseIPv4
 -BindIP - The ip address to bind to
 -Port  - Optional port number to connect to. Default is 8400
 -n     - Number of runs
 -t - For running continuously until Ctrl+C is encountered.
 -i - Interval in seconds between two consecutive runs. Default is 1 second

 Example: cvping Machine.Comp.Com -UseIPv4 -Port 8402 -n 5 -i 2

Thanks,

Stuart

Hello,

This looks like restore from snap operation. We will need logs to look into further but my guess some left over operation is causing this issue.

can you please check CVD.log for errors.