This post is more than 5 years old
1 Message
0
2237
April 24th, 2012 07:00
VM Type Client Backups Failing
We have several VM client backups that fail on a regular basis. Some days the jobs will run without any issues and then some days they fail with this message:
savegrp: suppressed 24 lines of output.
Temporary vmMntLoc Directory for VADP created.
Performing the backup via the Virtual Center.
Application information attribute VADP_VM_NAME for client WMH-CRM-DC03 is set to "WMH-CRM-DC03".
Trying to connect to the VM using VM name 'WMH-CRM-DC03'.
Performing a File level incremental over image level backup.
Creating snapshot for WMH-CRM-DC03.
Creating snapshot for 'vm-1245' ...
74854:nsrvadp_save: The following VMware related error occured: Unable to create snapshot '_VADP-BACKUP_' for VM: vm-1245. Details: 'An error occurred for task 'CreateSnapshot_Task'. Details: Unable to communicate with the remote host, since it is disconnected.'.
80405:nsrvadp_save: Could not create Snapshot for VM 'WMH-CRM-DC03'.
Temporary directory 'c:\mnt\WMH-CRM-DC03' for VADP deleted.
I am new user to Network and this is a new install; have not been able locate this message in Powerlink.
Clifton
0 events found
Bebo2k
544 Posts
0
April 24th, 2012 16:00
Hi Clifton,
First of all make sure that you add the VADP_VM_NAME variable in the Application Information attribute of each NetWorker virtual Client resource Correctly. The variable format is entered as VADP_VM_NAME=vm1
Where vm1 is the display name of the VM used in the vCenter
VADP_VM_NAME is case-sensitive. For example, if the VM host name is upper-case (such as SuSe11-X86), the value of VADP_VM_NAME must be set to SuSe11-X86.
For the “Unable to communicate with the remote host, since it is disconnected” error message, you have to verify that there is no communication, or DNS issue between the Backup Server, Storage Node, ESX Server, or Virtual Center server.
I had this issue before and I solved by deleting the Virtual Machine from inventory (right click on the VM and select “Remove from Inventory”). Do not delete from disk Then, re-add the VM by browsing the datastore holding that VM, right clicking on the VMX file and selecting “Add to Inventory”.
Hope that helps to solve the issue.
Thanks,
Ahmed Bahaa
Bebo2k
544 Posts
0
April 24th, 2012 16:00
Also check you vSphere license, and please have a look as well on the following Powerlink article:
https://solutions.emc.com/emcsolutionview.asp?id=esg121746
Thanks,
Ahmed Bahaa