Veeam Agent for Windows (licensed) failed jobs

[zadrian]

I keep having this failed job (8 devices) when 1 or 2 devices cannot send backup job config to "devicename". cannot conenct to "devicename".
But when I see the success menu, the machines shows status as successful.

Then I also double check the Inventory menu....I have the following
1. 3 PCs (of the 8 installed) are offline for at least 3 days (3, 3 & 4 days respectively). But can ping the host names.
- The PCs were powered off the past few days (friday, Sat & Sun).
- If I do an agent rescan, they disappear from "offline"

[Dima P.]

Hello zadrian.

What job type you are refering to (managed by backup server or managed by agent)? Thanks.

[zadrian]

What is the difference ?
The job is seen as "Windows Agent Policy" in VBR server.

[Dima P.]

zadrian,

Managed by agent job collects statistics after every rescan, so the state of your agent activity might be outdated. With managed by backup server job type agent instantly updates job stats since jobs is controlled by Veeam B&R server.

[zadrian]

I installed the agent via the VBR server through the "inventory" and the machine was added into the backup policy. Would this be VAWW (licensed for 50 machines) controlled by the VBR (licensed for VMware for 13 sockets) ?

[Dima P.]

Yes, thats correct.