I saw this problem when customer moved virtual clients to different lun, some moved machines appear as new one. You can check it when you try to add machine to avamar again, or you can check it in policy in client properties if you will see lun. I have retired old clients and add it again.
The weird thing is when you go to "Import multiple clients" into the domain under Administration, the VMs with the "No VM" error show as already added (they are greyed out).
I dont know why Avamar Server cannot reestablish the communication with vCenter. but in my environment I solved this:
Open Avamar Console > Administration button > Services Administration Tab > open tree e go to utility node > on right pane locate your vcenter > right click and select "Restart yourvcenter.com".
In my case the backups working again after this. good luck
I had this issue and we resolved it by Launching the MSC and in the administration/ Service administration / module / UtilityNode. restart the ConnectEMC service. Support basically told me that the node temporarily lost connection with the Vcenter. It fixed the problem for about a week. Then I move the Guest to another datastore and since then started getting it again. For some reason I see this a great deal with Cloned servers as opposed to servers built from scratch
The only way I found to get it back is to go into Avamar Administration and Retire the client in question, keeping the data for the retention period. In that same screen (Avamar Administration), highlight the VMware V-Center Domain and right click. Select NEW CLIENT and it will open another window. Client Type should be VMware Virtual Machine. Click on BROWSE to look for the new client. In the Virtual Machines window and under the VSPHERE VIEW, click on Host and Clusters. Go to the LEFT PANE and look for the ESX Host that the VM resides on. Left click on ESX Host and Left Click on the Virtual Machine and click OK. You will need to do this because you can not locate the Virtual Machine under the list of Virtual Machines. For some reason, the Virtual Machine is not showing up where they should, under the Virtual Machines and Templates section..
fdxpilot
2 Intern
•
143 Posts
0
July 26th, 2012 19:00
Found the GUID in mcdb using this query:
select cid, vm_real_name, uuid from vm_client where vm_real_name = 'nameofvm' ;
It is different from the current GUID per vSphere. Any way to get these back in sync?
Lucky85
173 Posts
1
July 26th, 2012 23:00
Hello,
I saw this problem when customer moved virtual clients to different lun, some moved machines appear as new one. You can check it when you try to add machine to avamar again, or you can check it in policy in client properties if you will see lun. I have retired old clients and add it again.
Regards
Lukas
fdxpilot
2 Intern
•
143 Posts
0
July 27th, 2012 08:00
The weird thing is when you go to "Import multiple clients" into the domain under Administration, the VMs with the "No VM" error show as already added (they are greyed out).
rodreis
1 Rookie
•
2 Posts
1
January 28th, 2013 15:00
I dont know why Avamar Server cannot reestablish the communication with vCenter. but in my environment I solved this:
Open Avamar Console > Administration button > Services Administration Tab > open tree e go to utility node > on right pane locate your vcenter > right click and select "Restart yourvcenter.com".
In my case the backups working again after this. good luck
gherrington
1 Message
0
April 23rd, 2013 09:00
I had this issue and we resolved it by Launching the MSC and in the administration/ Service administration / module / UtilityNode. restart the ConnectEMC service. Support basically told me that the node temporarily lost connection with the Vcenter. It fixed the problem for about a week. Then I move the Guest to another datastore and since then started getting it again. For some reason I see this a great deal with Cloned servers as opposed to servers built from scratch
rmartis
6 Posts
1
April 23rd, 2013 12:00
The only way I found to get it back is to go into Avamar Administration and Retire the client in question, keeping the data for the retention period. In that same screen (Avamar Administration), highlight the VMware V-Center Domain and right click. Select NEW CLIENT and it will open another window. Client Type should be VMware Virtual Machine. Click on BROWSE to look for the new client. In the Virtual Machines window and under the VSPHERE VIEW, click on Host and Clusters. Go to the LEFT PANE and look for the ESX Host that the VM resides on. Left click on ESX Host and Left Click on the Virtual Machine and click OK. You will need to do this because you can not locate the Virtual Machine under the list of Virtual Machines. For some reason, the Virtual Machine is not showing up where they should, under the Virtual Machines and Templates section..