-
- Veteran
- Posts: 536
- Liked: 111 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Typo when enabling/disabling Windows Agent Job?
Hi,
when you enable or disable a Windows Agent Job in V12 it shows the message 'Enabling selected policies' and 'Disabling selected policies'. However, when you enable or disable a Linux agent job or any other job it shows 'Enabling/Disabling selected jobs'. It this difference (policies vs jobs) on purpose or a typo?
when you enable or disable a Windows Agent Job in V12 it shows the message 'Enabling selected policies' and 'Disabling selected policies'. However, when you enable or disable a Linux agent job or any other job it shows 'Enabling/Disabling selected jobs'. It this difference (policies vs jobs) on purpose or a typo?
-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
Hello Franc
It doesn't depend on the protected operating system. The prompt will show you the right message (job/policy) for the chosen job mode.
Backup Job = Agent job mode "Managed by backup server"
Backup Policy = Agent job mode "Managed by agent"
Best,
Fabian
It doesn't depend on the protected operating system. The prompt will show you the right message (job/policy) for the chosen job mode.
Backup Job = Agent job mode "Managed by backup server"
Backup Policy = Agent job mode "Managed by agent"
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 536
- Liked: 111 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
I think it's the other way around? We have agent jobs managed by the backup server and those show 'policies'. The Linux agent job managed by the agent shows 'job'.
-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
No, it was correct.
With managed by backup server, the job is created on the backup server. Because the backup server manages the job.
When you choose Managed by Agent, we need to get the job to the Agent. Therefore it's a policy. When the policy is applied to the agent, a Backup Job gets created on the Agent.
Backup Job = Agent job mode "Managed by backup server"

Backup Policy = Agent job mode "Managed by agent"

Best,
Fabian
With managed by backup server, the job is created on the backup server. Because the backup server manages the job.
When you choose Managed by Agent, we need to get the job to the Agent. Therefore it's a policy. When the policy is applied to the agent, a Backup Job gets created on the Agent.
Backup Job = Agent job mode "Managed by backup server"

Backup Policy = Agent job mode "Managed by agent"

Can you please share a screenshot? That doesn't sound right to me.We have agent jobs managed by the backup server and those show 'policies'. The Linux agent job managed by the agent shows 'job'.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
I believe I see what you are talking about now.
This should be "Enable selected jobs". I will report it.

Thank you.
Fabian
This should be "Enable selected jobs". I will report it.

Thank you.
Fabian
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 536
- Liked: 111 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
That's indeed what I mean 

-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Typo when enabling/disabling Windows Agent Job?
Hi Franc
Thanks for reporting it.
We plan to fix it in our upcoming version (v12.1).
Best,
Fabian
Thanks for reporting it.
We plan to fix it in our upcoming version (v12.1).

Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 18 guests