Return
-
Title
When VM is removed from backup group using Powershell, the VM disappears from GUI, but not from DB -
Description
When a VM is removed from a backup group using the vRanger cmdlets, the VM disappears from the GUI, but remains in the database. If backup jobs are run, the deleted VM is still backed up. If the vRanger service is restarted, then the deleted VM reappears. -
Cause
vRanger PowerShell cmdlet insufficient to mark VMs in backup groups as deleted in vRanger SQL DB.
-
Resolution
Use command below, which has a 3 line SQL command which when is run from PowerShell after the cmdlet 'Remove-BackupGroupMember' command. This should take care of the orphaned VMs and update the database. There should then be no more duplicate VMs backed up when part of a backup group.
$mycommand='use vRangerPro;update BackupGroupMembers set IsDeleted=1 where NodeName="'+$vm.Name+'" and InventoryNodeVirtualizationObjectId="'+$vm.VirtualizationObjectRefID+'" and IsDeleted=0'
echo $mycommand >temp.txt
sqlcmd -S <192.168.0.1>\vRangerPro -U <user> -P <pass> -i temp.txt -
Defect ID
14819