No destination type (Case 04831327)

[caras]

Hello,

I'm trying to run Veeam endpoint (newest release) at Linux Suse Leap 15.2.
Configuring a backup job stops for me at the tab "location": I cannot go to next tab after selecting the target media.
The field "type" of the destination media is erroneously always empty, although its size is retrieved correctly.

Here is a screen shot: https://nc.caras.net/s/HerJgREqCf4mEq6

It affects all types of my external media: hard disks and memory sticks. The target media are mounted as fuseblk, nothing special.

Is there a way to fix that?

[Natalia Lupacheva]

Hi,

I see your case is closed due to high load of the Support team, but you can try again later.
Also, do you see any errors when you try to click "Next"?

Thanks!

[caras]

No, there is no message. Nothing happens if I click at "next": it is like a disabled control.

Btw: Quietly closing a support case is an unprofessional and rude behavior.

[Natalia Lupacheva]

Hi,

Unfortunately, email support for free products is provided on a best-effort basis depending on staff availability. You receive this information when the case is closed.

May I ask you to clarify the exact Agent version you use?

Thanks!

[PTide]

Please try to use CLI to create a job targeting the same location and see if the issue affects CLI as well. I have a feeling that that could be simply a UI glitch.

Thanks!

[caras]

@Natalia Lupacheva:
Its version 5.0.0.4318, the newest I can get from Veeam repository.

I got a confirmation mail from Veeam when I opened the case, but not that it has been closed.
I'm not convinced the problem only occurs with free license...

@PTide:

Code: Select all

# veeamconfig repository create --name USBDisk --location /run/media/me/Veeam
Cannot find the mountpoint information for device number [8:17]

The backup properly worked at the affected computer until spring 2021, then the situation degraded, either caused by a system update or by a Veeam update.
The former backup job did not work anymore, that's why I deleted it and now I'm unable to recreate it.
So likely not only the definition of the backup job is disturbed.

[PTide]

Hi,

I slipped a note to our support team to reopen the case and look at it closely.

Thanks!