Removing Physical Server from Unmanaged

[nunciate]

I have a physical server that was no longer being backed up but not removed before upgraded to 9.5U3
It is still showing under unmanaged and I would like to remove it completely. I can find no way to do that.

All jobs, disk data and other references to the VM are removed but it still shows up under unmanaged.

[Shestakov]

Indeed, looks like there is no way to "forget it". If it bothers you, ask support team to delete it form database.
Do you have scheduled rescan by IP range, CSV or AD?

[nunciate]

All of the computers that showed up under unmanaged where previous version 1.5 agents I had installed. I was able to upgrade and move all of them into new Protection Groups and then into new jobs with no issues.
I still had that last one available so I powered it up, upgraded it, moved it to a protection group and job. That removed it from unmanaged so I then removed it from the job and protection group and powered it back off.

All fixed but would like to make a feature request to be able to right click and remove systems from unmanaged.

[tsightler]

If you create a temporary protection group, add this unmanaged host to it, and them immediately remove the protection group, it should be deleted. A little weird, but works and might save you a support call.

[Shestakov]

Nice workaround, Tom.
Make sure you don't discover it back with rescan.

[tsightler]

I've had to do this for a number of orphaned host from old agents that doesn't exist anymore, both in my lab and in a few customer setups as well. As long as you've removed all other references to this host, like any backups, left over unmanaged "jobs", etc, it won't come back.

[stuartmacgreen]

I have a case scenario for right-click remove Unmanaged host 'feature'

We have leased server hardware. It was being protected by Veeam Agent for Windows 2.0 under Veeam B&R 9.5u2
The hardware was replaced in January 2018
Good time to perform a VAW restore to new hardware. Success.

Now in Veeam B&R 9.5u3 I have two entries for SAME host name under Unmanaged group. One of the entries shows status Installed, other Not installed.

How do I remove Not Installed (old hardware) using this workaround - it will surely remove both entries? Or is it a call to Support to remove.?

Thanks

[stuartmacgreen]

... when I try (old hardware entry) to Move to » New Protection group it says

Unable to move the host to a protection group because the host is managed by service provider.

[Dima P.]

Any chance you used Veeam Agent for Windows together with Veeam Availability Console or Veeam Plugin for LabTech? Thanks.

[stuartmacgreen]

No to both.
Thanks

[Dima P.]

Kindly, open a support case and let our engineers check the application logs. Do not forget to include the case id in this thread. Thank you!

[stuartmacgreen]

Support ID #02770176

[nuraz19]

I had the same issue and here is the solution. Hope it helps:

Go to Manually added protection group and on the Computers tab remove the host that been shutdown. Then next next Finish. That will remove the offline host from the list and will stop annoying error email.

[stuartmacgreen]

SOLUTION: Using Veeam Agent for Windows 3.0 Standalone and VBR Repository. Veeam 9.5 Update4a

Symptoms:
Physical Veeam Agent for Windows hardware is decommissioned.
Backups are no longer required.
Remove all trace of Agent within Veeam

How to remove Agent from Veeam Backup & Replication.
Agent is listed under Inventory > Physical & Cloud Infrastructure > Unmanaged
Agent Backup Job listed Jobs > Backup
Agent Backups listed under Backups > Disk

1. Delete from Disk the Agent Backups
2. Delete the Agent Backup Job. This will also delete Agent from Unmanaged.
3. Check Agent no longer appears under the Unmanaged view.

Thought I would update this post as I came back around to same scenario. Deleting the Agent Job removes the entry. May seem simple writing this.

[juanmachado]

If you create a temporary protection group, add this unmanaged host to it, and them immediately remove the protection group, it should be deleted. A little weird, but works and might save you a support call.

That did the trick!

Thanks!