During the Rescan of a Protection Group, a machine displays the warning:
Agent is managed by another Veeam server (<other_Veeam_server>)
If the Veeam Backup Server listed in the warning is valid and is intended to manage the machine, remove the machine from the protection group on the Veeam Backup Server where the warning occurred.
If the intent is to migrate the machine's management from the other Veeam Backup Server to this new Veeam Backup Server, first remove it from all jobs and protection groups on the other machine.
Typically, once a machine has been removed from all jobs and protection groups on a Veeam Backup Server, records tying that Veeam Agent deployment to that Veeam Backup Server should be removed.
However, if the Veeam Backup Server managing the Veeam Agent deployment is no longer available or has been decommissioned, perform the following procedure to reset the Veeam Agent configuration, forcing it into standalone operation mode.
Note: These steps should not be performed if the managing Veeam Backup Server is still active and accessible.
These commands are fully documented in the links above.
For Veeam Agent for Microsoft Windows, open an Administrative PowerShell prompt and execute:
If the Veeam Agent for Microsoft Windows deployment was operating in Managed by Server mode, the above command will exit with code 3:
Unable to set agent to self-managed mode because this backup agent is already managed by the backup server.
Use the Manual Standalone Reset Script below to forcibly untether the Veeam Agent for Microsoft Windows deployment from Veeam Backup & Replication.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case