Unsolved
This post is more than 5 years old
4 Posts
0
636
Clients got disabled automatically from VM Protection Policy
Last week, Our windows team did some activity on the VSphere client, We suspect due to this change, VM's from one of the VM Protection policy got disabled by itself from one of the VBA, We were unable to identify this for a week. So there were no backups for these clients.
Can some one help us to identify if any Clients gets disabled automatically from VMware Vsphere or VBA?
Karthik_N1
25 Posts
0
March 21st, 2017 00:00
Hi TCS backup team,
Please make sure the VMs are present in the EBR's database by issuing this command on your VBA SSH putty.
mccli client show --recursive| grep -i VMname
If they are still there, nothing to worry.
https://community.emc.com/message/882013
Check if they are deleted and then retire it from VBA:
mccli client retire --name=
Kushal26
4 Posts
0
March 21st, 2017 02:00
From the above commands we can only identify whether the VM is active or not from the VBA Putty login. However, I would like to know is there any alert or automatic mechanism to determine whenever any VM gets disabled/deleted from VSphere Client with out our knowledge.
Is there any script that we can run to determine the changes that was performed on VSphere Client or VBA? Suggest pls.