commvault.com commvault.com
Solved

Error 91:32 When Trying to Restore a VM

Show first post

31 replies

Damian Andre
Rank
Userlevel 7
Badge +23

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 ;)

T
Rank
Userlevel 3
Badge +6

Its NFS. I can recover from our Production system, but the vault copies on our Storage system are failing. 

T
Rank
Userlevel 3
Badge +6

Hey @tsmtmiller .  Wasn’t able to find the CV case number.  Were you able to get this resolved?  IF so, can you share the solution here?

Thanks!

Thanks

CV closed the case so the 3rd party support is reopening a case with them. I uploaded a new log yesterday, its the same error. I have a feeling it’s something on VCenter as I see some errors during the restore in vcenter under the monitor section:

“Error caused by file <esx backup>

“Datastore <esx backup> is not accessible . “No connected and accessible host with required privilege is attached to this datastore”

 

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

Hey @tsmtmiller , following up to see if this issue is resolved (and how).

Thanks!!

https://www.linkedin.com/in/michael-struening
Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

Appreciate the update.  If you can get the CV case number I can track it.

https://www.linkedin.com/in/michael-struening
MichaelCapon
Rank
Userlevel 6
Badge +14

Guessing this is VMware, I would suggest to try manually mapping the Snap to the ESX (From Array Management) and check if works okay first.

Also, If using NFS it may also be worth checking in VMware the the Host you are mapping to hasn’t reached the limit of volumes. - https://kb.vmware.com/s/article/2239

Best Regards,

Michael

Reply


Terms & ConditionsCookie settings