Only default backup repository available (Agent 2.0)

[cxwsrei]

Hi all
I set up a backup with the objective to use the backup repository of the veeam 9.5 backup&recovery.
We have on the veeam backup server 2 backup respositories:
"Default backup repository" - currently on drive C:
"Second backup repository" - this is located on drive D: - this is used for proction backups.

When I set up the (test) backup via Agent 2.0 ONLY the "Default backup repository" is offered as an available backup repository !?!
1) Why is the "Second backup repository" not available also (Both are of type "Windows") ?

2) On the "Configure Backup" pane of the backup configuration (via agent) I tried to issue user/password credentials.
This has been refused with "Unable to obtain a Veeam Agent for Windows license from the backup server".
Any idea what is the restriction here ?

According the document "veeam_agent_windows_2_0_editions_comparison".pdf ALL backup repositories are available for all version - for the free version as well as for any other version !?!

[DGrinev]

Hi and welcome to the community!

1) Please can you check agents permissions on the secondary repository.
2) What version of Veeam B&R are you using?

Thanks!

[cxwsrei]

Hi
thank you for the quick response.
The link is helpful - unfortunately this information does not solve my problem.
The "Agent permissions" property is only available on the "Default repository" that is currently assigned to drive C:
But not to the big repository (36 TB internal disk (cabinet)) - assigned to D:
Maybe due to the type of drive - I still have to continue evaluating about that topic.

Regards

[Mike Resseler]

Hi,

So the agents permission menu option is not seen on the other repository in B&R? Can you try to use CTRL and right-click on that repository and see if the menu item appears?

Mike

[nielsengelen]

Maybe due to the type of drive

Could you also explain what you mean by this?

[cxwsrei]

Hi Mike

I read already about the option with the CTRL key - unfortunately no success.

@vmniels: I think you can ignore my annoation about the type of drive - I thought I read already that there are some restrictions. But I reopened the web site whre I thought this information can be found - but it is not there.
Consequently my fault - I "merged" some informations in my mind by accident. Sorry.

[Mike Resseler]

If you can use that repository for B&R jobs but cannot select it for VAW, then there is something wrong for sure.
I suggest you log a support call so our engineers can go through the logs and investigate why this is not possible
Please post the case ID and follow-up here.

Many thanks
Mike

[cxwsrei]

Hi Mike

I would .. if I could .
When I try to open a case via the support form of Win 2.0 Agent I´m refused - obviously due to the e-mail adress verification - I don´t pass !?!
Seems it checks if I´m a registered customer for a licensed version of Win Agent !?!
On the other hand the comment on the form amkes me believe that a case can be issued by everyone - just a feedback is not guaranteed !??!
Strange

[cxwsrei]

Mike
ignore my last comment.
Meanwhile I got a confirmation mail.
Now I succeeded to send my case.

Regards

[Mike Resseler]

Super! I was just typing the procedure and you saved me a few minutes doing so

[SKratzTS]

Is your large Repository tied to a scale-out repo by any chance? If I recall, scaleouts aren't supported as VAW destinations..

[skochetkov]

Is your large Repository tied to a scale-out repo by any chance? If I recall, scaleouts aren't supported as VAW destinations..

Hello, this is not so: VAW 2.0 is able to use SOBR.

[cxwsrei]

The problem is solved - veeam support has shown me how to solve it.
The problem was that the 2nd respository was not released/permitted for agent use.
The agents permission menu option could not be found directly on the respository under "Backup Repositories" but under "Scale-out Repositories".
Simple cause - you just must know.

[Mike Resseler]

Ah, yes, I didn't think about that

And now that I look to it, this is nowhere told in our documentation which means I am going to ask to add that tiny detail in the documentation

Glad to see it is solved and thanks for coming back with the solution.

Cheers
Mike