The Backup Agent workflow is as follows The management agent connects, then the Veeam console detects the agent and, to complete the process, you need to apply a backup policy to that agent from the console.
The "not_configured" status you see is the expected state until the policy is applied correctly.
Steps you should follow:
Open the VSPC console.
Locate the agent in the console.
Assign the backup policy Once you have located the agent, select the option to "Assign" a backup policy. When the policy is applied, the agent's status in your client area will change from "not_configured" to "configured".
The "Standalone" mode indicates that the agent is not being centrally managed by the VSPC. For it to work with the Backup Agent service, the agent must be in "ManagedByVAC" mode to receive the automatic backup policy that OVHcloud assigns to this service.
The assignment of the backup policy is not performed from the server's command line, but from the VSPC web interface that you can access from your client area.
Do the following:
Access the VSPC console of your tenant.
Locate the agent in the console Within VSPC, go to the "Managed Computers" section and open the "Backup Agents" tab. You should see your server in the list, with a status indicating it is ready to be configured, such as "Discovered".
Assign the backup policy Select the agent corresponding to your server in the list and click the "Assign" link at the top of the list. A window will open where you must select a backup policy. Once selected, click "Assign" to apply it.
Once the policy is assigned, the agent's status in the VSPC console should change, and the OVHcloud panel should no longer show the not_configured status.
Also, if you run veeamconfig mode info again on your server, the mode should have changed to "ManagedByVAC", confirming that the agent is now under the centralized management of the backup policy.
What I've been able to see is that, by design, the backup policy assignment process in OVHcloud's Backup Agent is intended to be automatic. The steps I outlined earlier would be the standard procedure in a typical VSPC console, but according to OVHcloud documentation, the VSPC user does not have permission to perform this action.
I recommend contacting support, explaining that the agent is installed and connected, but that the Backup Agent remains in the "not_configured" state.
The management agent connects, then the Veeam console detects the agent and, to complete the process, you need to apply a backup policy to that agent from the console.
