Attempt to work with Backup Group (BG) crashes UI.
BG consists of several VMs. One or more do not exist any more or reside on disconnected ESX host. Ranger is trying to get information on these VMs using VMware API calls.
Below is a temporary workaround while bug is being investigated and fixed. Following SQL statements should be executed through MS SQL Management Studio or sqlcmd
1. List all VM in the BG
USE vRangerPro
SELECT bg.backupgroupid, bg.backupgroupname, bgm.nodename FROM backupgroup bg
INNER JOIN backupgroupmembers bgm ON bg.backupgroupid = bgm.backupgroupid
WHERE bg.isdeleted = 0 AND bgm.isdeleted = 0
ORDER BY bg.backupgroupid
2. 3rd column will display VM name. If you know what VMs do not exist anymore or disconnected somehow, run following statement using VM names correspondingly:
USE vRangerPro
UPDATE backupgroupmembers SET isdeleted = 1
WHERE nodename IN ('<VM_name_1>', '<VM_name_2>')
3. Restart vRanger (main) Service, reopen GUI. You should be able to work with BG.
