Bug / unexpected behaviour report on vsa v13

[tinto1970]

HI all, scenario: VBE13 Linux appliance build 13.0.1.2067

I am adding a linux VM to have a mini repo for configuration backups. No need of vPower NFS.
I have only one windows machine managed by this VBR server, out of date/not working for some reason

When creating the repo, it's impossible to proceed because it's not permitted to create the repo itself with vPowerNFS disabled. This happens on the Web Gui AND with the client.
I can unselect the vPower configuration BUT it's not allowed to save this configuration because the windows mount server is out of date. It makes naturally no sense to block the creation of the repository: the non-working windows server is NOT needed by this configuration.

https://ibb.co/67WfC5b8

thanks for your attention

[Mildur]

Hi Alessandro

I can unselect the vPower configuration BUT it's not allowed to save this configuration because the windows mount server is out of date.

If this machine has components that are reported as out of date, such as leftovers from a previous installation, then this error message is expected. You must clean up the Windows server before adding it as a managed server and backup repository. If the Windows server is not currently added to any backup server, remove all Veeam components manually (Windows Settings → Apps / uninstall software).

If you still see the error afterward, please contact Veeam Support so we can investigate why an “old component” is still being detected.
Don't forget to provide us with the case number.

Best,
Fabian

[tinto1970]

hi Fabian!

Yes I know how I should troubleshoot it, but I don't want to do it (long story, it's a lab)

another screenshot: if I don't want to enable vPower NFS, why should I specify a cache directory?

https://ibb.co/39g765Nb