Issue with RHEL 7.9 after update to veeam 5.0 Linux agent

[eidal]

Hi,

I have a RHEL system with kernel 3.10.0-1160.15.2.el7.x86_64 (I also have the subsequently kernel-devel and kernel-headers libraries).
I use the Community version of Veeam for Linux and it was working like a charm since a

Code: Select all

yum update

which installed the new version of the agent.
I back up the whole system to an external hard drive.

Now, when using the backup wizard, the latter does not want to pass to next when entering the path to which to backup the system.
I have deleted all jobs, all repositories, made a clean install and I then used the command line thinking that the problem would be GUI dependent...

When using

Code: Select all

veeamconfig repository create --name rhel_backup --location /run/media/<user_name>/<HDD_name>/<backup_folder>

I have the following error :

Code: Select all

Cannot find the mountpoint information for device number [8:2].

I have verified the mount point using

Code: Select all

mount -l

and everything seems to work...

Code: Select all

/dev/sda2 on /run/media/<user_name>/<HDD_name> type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [<HDD_name>]

Would someone please help me ? Would someone had face the same situation ?
Thanks in advance,
Best regards,

[HannesK]

Hello,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic (also community edition can open cases).

Without case number, the topic will eventually be
deleted by moderators.

Best regards,
Hannes

[eidal]

Hello,
I do not have an ID as I use the community edition. I have a free license. Unless I have misguided myself on what is a case ID...
Anyway, I was happy with your solution but apparently the new version is buggy on RHEL 7.
Before closing it would you please inform me on how to rollback to Veeam 4.x and prevent further update ?
Thanks,
Best regards,
Alexandre

[Andreas Neufert]

Please open a support ticket on www.veeam.com/support and share the ticket number here.
Community edition has best effort support.

[eidal]

Thanks for the link I had found it previously. My ticket number is #04690557.
I understand.

[PTide]

Hi,

Before closing it would you please inform me on how to rollback to Veeam 4.x and prevent further update ?

Just uninstall the existing version and install v4.
Since you use RHEL you can simply disable veeam repo with the following command:

Code: Select all

yum-config-manager --disable veeam

Thanks!

[eidal]

Hi thanks,
I originally wanted to have a fix for the 5.0 version but I rolled back to 4.0.1.2365-1.el7 and it works... it is indeed a bug in the new February patch.

For whom it may concerns the steps are the following:
- Download the wanted version at http://repository.veeam.com/backup/linu ... /7/x86_64/.
- For a full new install, I have selected :

• kmod-veeamsnap.4.0.1.2365-1.el7.x86_64.rpm

• veeam.4.0.1.2365-1.el7.x86_64.rpm

• veeamsnap-ueficert.4.0.1.2365-1.el7.x86_64.rpm

- Uninstall all previous version : run

Code: Select all

rpm -qa veeam

to get the version. And then

Code: Select all

rpm -e <package_name>

- First install the kmod and veeamsnap due to dependencies issues. Install with

Code: Select all

rpm -ivh <package_name>

- Install veeam with the previous command
- Ban veeam repo from yum config manager as suggested from @PTide
- Reboot PC in order to apply kernel changes
- Enjoy a working version in RHEL 7.9