Views:

Summary

An agentless backup job fails with messages reporting connection or networking issues. For example: The server refused connection.

 

 

Symptoms

 

 

During an agentless backup job, the following message displays:

 

 

x.x.x.x <date/time stamp> SNBSVH_658E Task X encountered error. Error message:There has been some problem while running VM Backup task, reason (java.lang.Exception: All the disks have encountered errors)

This generic error message and can be ignored in most cases. Wait for the job to fail, then examine the error messages that display at the end of the job summary. For example:

x.x.x.x <date/time stamp> SNBSVH_826E ............Extended error: There has been some problem in processing disk ([VM name] <data store>/*.vmdk), reason (The server refused connection)

This error message confirms that the job failed due to a connection, networking or communication issue.

 

Resolution

 

 

Most messages originate from the underlying VMWare environment, indicating that the issue stated in the error messages should be resolved at that level as well. In this case, the server named in the error message is most likely one of the ESX(i) hosts.

 

 

Perform the following steps to resolve the issue:

  1. Through vMotion, move the virtual machine named in the message to another host. Once complete, run the job again. The job usually completes successfully. Investigate the underlying communication issue in the virtual infrastructure.
  2. Explicitly select a proxy for the backup job while testing multiple proxies to see if the communication issue appears with more than one proxy. To explicitly select a proxy:

    a. Open the agentless backup job definition in the NSB management console.

    b. Select Set Proxy.

    c. Clear the Automatically Select Proxy check box.

    d. Select Explicitly Select Proxy.

    e. Save the job definition and run the job again. Repeat these steps using different proxies.

Note: The first step usually resolves the issue. Some of the above steps are performed on the VI client, outside of NSB. If you are unsure of how to perform these steps, ask the user to consult a VMWare expert.