Skip to main content
Solved

Live Recover and Live Mount error

  • December 27, 2022
  • 1 reply
  • 924 views

Forum|alt.badge.img

Hi 

 

we are currently setting up a Test Environment to test Live Mount and Live recovery functionality in Commvault. 

 

When trying to Live Recover a previously backed up VM we get the following error message:

Tdfs::TdfsConfigClient::SendCommand(1854) - Error attaching to server. [0x80070057:{CCvNetwork::Attach_RemoteService(1770)} + {CCvNetwork::Attach_RemoteService(1713)} + {CCvNetwork::Attach_RemotePort(1351)/W32.87.(The parameter is incorrect. (ERROR_INVALID_PARAMETER.87))-Port passed is not valid. [3dfsService/0/0].}]

Tdfs::TdfsConfigClient::Start3dfsServerWithWait(1389) - 3dfs server failed to start. ret [-16]

CreateNASDatastore() - PlatformConfigFaultFault Exception - [An error occurred during host configuration.] - [Mount failed: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Unable to connect to NFS server]

For a Live Mount we get:

VmOperation::LiveMount() - LiveMount Operation with error code [125], error message[Mount failed: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Unable to connect to NFS server Operation failed, diagnostics report: Mount failed: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Unable to connect to NFS server Refer https://kb.commvault.com/article/67989 for more information to resolve the issue.]

vAppWorker() - LiveMount operation failed with errorCode [318769636]

We assume this could be due to a firewall rule preventing the mount of the NFS datastore. Are there additional port requirements for this to work? Or could this be due to any other configuration error on our side?

 

Thanks a lot in advance.

Best answer by japplin

Hi @Alex Zett ! For NFS connectivity, you would have to check/confirm port 2049 is available for communication between the MA/proxy and the ESX host accepting the mount request. Previously in the past as well, we’ve noted that port 111 may need to be used for TCP/UDP communications, if the NFS version is older than v4. 

 

https://kb.commvault.com/article/67989 

View original
Did this answer your question?

1 reply

Forum|alt.badge.img+2
  • Vaulter
  • 3 replies
  • Answer
  • December 27, 2022

Hi @Alex Zett ! For NFS connectivity, you would have to check/confirm port 2049 is available for communication between the MA/proxy and the ESX host accepting the mount request. Previously in the past as well, we’ve noted that port 111 may need to be used for TCP/UDP communications, if the NFS version is older than v4. 

 

https://kb.commvault.com/article/67989 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings