Unsolved
This post is more than 5 years old
1 Rookie
•
100 Posts
0
6621
October 24th, 2013 07:00
Avamar 7 vmware synchronization
Hello,
we are using avamar7 for vmware backups, We have created a new container for a vmware group resource. Newly added virtual machines to that group automatically added to avamar backup group without any problem but removed virtual machines from vmware not updated. Also you cannot remove it from avamar administration gui manually. Client is no longer available in vmware but avamar does not recognize it. Is there anybody faced with similar issue ?
Thanks.
No Events found!
emcmobile_ws
19 Posts
0
October 28th, 2013 02:00
not yet
ionthegeek
2 Intern
•
2K Posts
0
November 14th, 2013 16:00
I would recommend opening a service request for this issue.
DELL-Leo
Community Manager
•
9K Posts
0
November 15th, 2013 00:00
Hey,
Do not encountered similar issue before. Suggest you to open a SR for this issue.
robert.williams
2 Posts
0
November 15th, 2013 04:00
Can2
1 Rookie
•
100 Posts
0
November 15th, 2013 06:00
Thank You all, I will open a sr, Then will update you.
niko.virta
51 Posts
0
January 28th, 2014 04:00
I have same issue with 7.0.0-427 ... how was this solved?
niko.virta
51 Posts
1
January 30th, 2014 07:00
Solution:
1. A dynamic container will always get updated whenever there is a new VM added to the container in vSphere side. Therefore, it is no meaning to delete a VM from the protected container, since MCS will add it back.
2. If the VM is deleted from the vCenter, MCS still keep the VM (and its parent relation) so that its backups can be used for restore later. MCS will not remove the VM because of the deletion in the vCenter.
If the user really wants to delete the VM from the dynamic container, he can transfer the container to static first so that the right-click menu for the container will be enabled for the deletion.
3. If you have deleted VM from VCenter but have like 6 months retention and want to keep backups for that long, you will receive "No VM" error as you can not "disable all backups" on the deleted VM (as there is no VM anymore) and you can't disable the group as the container has other VMs still running. This should have been fixed in 7.0.1-53.
Can2
1 Rookie
•
100 Posts
0
February 3rd, 2014 06:00
Problem solved after applying update1 in my case.
niko.virta
51 Posts
0
February 24th, 2014 12:00
You have the scenario 3 from my reply and still getting "No VM" error?
lborcher
1 Rookie
•
14 Posts
0
February 24th, 2014 12:00
I am on 7.0.1-61 but still the vm machine is still in backup failures as "no vm" is there any way to fix this other than remove container from dyanamic backups?
lborcher
1 Rookie
•
14 Posts
0
February 24th, 2014 12:00
Yes, that is correct and still the VM shows up, but still fails with “no vm”
Lyle Borcher
Enterprise Storage-BRS Administrator
Information Tech
Cabelas World Headquarters
Sidney NE 69160
308-255-2886
1 Attachment
image001.png
niko.virta
51 Posts
0
February 24th, 2014 13:00
Nice. Sounds like new SR then. Tell us the result afterwards how it was solved or is there new bug.