Feature Request: no error shown for hardened Linux repos

[cpfleger]

Hello,

When you use a hardened Linux repo (single use password) it will then be shown with an error sign in the GUI - see:

. https://ibb.co/StT1PKc
. https://ibb.co/1qq7nvX

Therefore I think it would be good if those Linux repos could be shown somehow else
but not with an error.

Regards!

[Mildur]

I cannot confirm this error. This is a issue in your environment.
In my environment, I don't have an Error Sign in the GUI for hardened Repos

Please open a Support Case to resolve that.

[cpfleger]

The problem is obviously a sideeffect of the problems that arise when running a new VBR installation migrating a BCO which originated from a v11 RTM (11.0.0.825).
Case number is #04810788

Regards!

[Mildur]

Most likely.
Something wrong in the database or veeam components on the Linux Server

[soncscy]

>The problem is obviously a sideeffect of the problems that arise when running a new VBR installation migrating a BCO which originated from a v11 RTM (11.0.0.825).

If I'm understanding you right, you installed Veeam "fresh" from iso and you restored from configuration backup of a base v11 version?

If so, guess it would mean that the cumulative patches must have gotten added to the installers and probably there is some disconnect between the cumulative patch components and the base release components. I guess you just need to probably re-authenticate the server and install the new components.

[cpfleger]

Whole story:
there has been a physical VBR at the beginning (vbr running RTM 11.0.0.825)
Migrated its config onto a new VBR (after installed 11.0.0.837 plus the patch from the latest iso first) running as a VM.
This is where I registered the Linux repo server to.

That VM had strange time sync problem (probably hardware problem of the host).

So I setup another VM on a different platform and migrates the BCO again.

I tried already (advised by support) a de-registration (as a simply update of the components didn't work) and a new registration - but Linux repo server is (still) flagged as outdated showing the installed binaries as v11.0.0.825

Something weird and wrong here, obviously when migrating from an old BCO (importing procedure showed no warning, problem or incompatibility).

Regards!